[Core] add parallel=1 as perf scenario for core #36582
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run python - core - perf |
|
/azp run python - corehttp - perf |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
No pipelines are associated with this pull request. |
kashifkhan
approved these changes
Jul 23, 2024
|
API change check API changes are not detected in this pull request. |
|
/azp run python - corehttp - perf |
|
No pipelines are associated with this pull request. |
|
/azp run python - corehttp - perf |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/check-enforcer override |
l0lawrence
pushed a commit
to l0lawrence/azure-sdk-for-python
that referenced
this pull request
Feb 19, 2025
* add parallel=1 as perf scenario for core * run parallel=1 scenarios by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding in parallel=1 to the perf scenarios, as many customers may not be parallelizing, as per @richardpark-msft's suggestion.