Increase timeouts for the CCS yaml suites #132357
Closed
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
benchaplin
added
>non-issue
>test
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
elasticsearchmachine
added
v9.1.2
v8.19.2
v8.18.6
and removed
v9.1.1
v8.19.1
v8.18.5
labels
elasticsearchmachine
added
v9.0.6
v8.19.3
v9.1.3
and removed
v9.0.5
v8.19.2
v9.1.2
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CcsCommonYamlTestSuiteIT has been muted on main for months and RcsCcsCommonYamlTestSuiteIT looks like it's getting close as well.
My limited understanding here leads me to believe this is as simple as: we're constantly adding yaml tests and therefore these CCS suites' timeouts need to be increased accordingly. Perhaps the test environment can be sped up in some other way but I think it's most important to get these tests running again.