-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Storage] Stress tests in pipeline? #21030
Conversation
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
sdk/storage/tests.yml
Outdated
displayName: 'Run Stress Scenarios' | ||
inputs: | ||
mavenPomFile: sdk/storage/azure-storage-perf/pom.xml | ||
options: -Dstorage-stress-scenarios |
There was a problem hiding this comment.
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.
sdk/storage/tests.yml
Outdated
@@ -47,6 +50,19 @@ stages: | |||
Path: sdk/storage/platform-matrix.json | |||
Selection: sparse | |||
GenerateVMJobs: true | |||
PostSteps: | |||
- task: Maven@3 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this 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.
/check-enforcer override (no this pr :( ) |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit ebd3e2c
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
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: