Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Storage] Stress tests in pipeline? #21030

Merged
merged 23 commits into from
May 18, 2021

Conversation

kasobol-msft
Copy link
Contributor

@kasobol-msft kasobol-msft commented Apr 28, 2021

This PR adds basic coverage for APIs that are potentially memory-greedy, so they don't become greedier while code evolves.

Things to follow up separately observed during this experiment:

@ghost ghost added the Storage Storage Service (Queues, Blobs, Files) label Apr 28, 2021
@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

displayName: 'Run Stress Scenarios'
inputs:
mavenPomFile: sdk/storage/azure-storage-perf/pom.xml
options: -Dstorage-stress-scenarios
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd either add $(DefaultOptions) or --no-transfer-progress to options to reduce the verbosity of this step.

@@ -47,6 +50,19 @@ stages:
Path: sdk/storage/platform-matrix.json
Selection: sparse
GenerateVMJobs: true
PostSteps:
- task: Maven@3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to run this task if the test run fails? Also, if this step fails do we want to fail the job?

Copy link
Contributor Author

@kasobol-msft kasobol-msft Apr 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can live with this not running if tests fail. We want to have green build. I'll check the later (but yes, we want to fail a job)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@mikeharder mikeharder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this works as a reliable test, it looks good to me.

@kasobol-msft
Copy link
Contributor Author

kasobol-msft commented Apr 29, 2021

/check-enforcer override (no this pr :( )

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@Azure Azure deleted a comment from check-enforcer bot May 17, 2021
@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft
Copy link
Contributor Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kasobol-msft kasobol-msft merged commit 32d85fb into Azure:master May 18, 2021
@kasobol-msft kasobol-msft deleted the resource-constrained-test branch May 18, 2021 22:14
@g2vinay g2vinay mentioned this pull request May 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants