[Build] Aggressively increase gradle based Test Cluster startup timeout #135672
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
We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced
breskeby
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
jozala
approved these changes
Sep 30, 2025
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Sep 30, 2025
…ut (elastic#135672) We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Sep 30, 2025
…ut (elastic#135672) We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Sep 30, 2025
…ut (elastic#135672) We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Sep 30, 2025
…ut (elastic#135672) We see plenty of errors due to a cluster not starting up. This is likely a combination of parallelism, memory pressure and to little timeout. This is aggressively increasing the timeout from 40 to 120s while we will monitor if the overall flakyness in ci is reduced
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.
We see plenty of errors due to a cluster not starting up. This is likely a combination
of parallelism, memory pressure and to little timeout.
This is aggressively increasing the timeout from 40 to 120s while we will
monitor if the overall flakyness in ci is reduced