[release/6.0] Schedule HTTP & SSL stress runs for release/6.0 #58272
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsBackport of #58262 to release/6.0 /cc @antonfirsov Customer ImpactTestingRisk
|
karelz
approved these changes
Aug 27, 2021
|
approved - infra changes necessary to ship. |
|
One approval from a person more experienced with infra would be nice to have before merging. Tagging @ViktorHofer and @trylek (Santi is OOF) |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #58262 to release/6.0
According to #58262 (comment), the YML entry requesting scheduled runs for
release/6.0has to live on therelease/6.0branch./cc @antonfirsov
Customer Impact
To make sure that NCL is stable for 6.0, we need to run and monitor our stress tests on nightly basis against the
release/6.0branch.Testing
N/A.
Risk
Low. This is a test infra change impacting NCL stress test runs only.