[Cosmos] Preserve circuit breaker test environment - #48207
Draft
tvaron3 wants to merge 1 commit into
Draft
Conversation
Restore pre-existing circuit breaker environment settings after availability strategy tests so later tests inherit the pipeline configuration. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 58eee70a-9712-4ccf-974e-f393a427e876
|
Azure Pipelines: Successfully started running 2 pipeline(s). 8 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
The availability-strategy tests previously set three circuit-breaker environment variables and then unconditionally deleted them. This removed the sign-off pipeline's
AZURE_COSMOS_ENABLE_CIRCUIT_BREAKER=Truesetting for every test collected afterward.Validation
Timeout note
The 900-second per-test timeout introduced in #47091 is already present. This PR does not change the separate 240-minute classic Azure DevOps job limit.