Increase Timeout in WaitForRefreshAndCloseIT #76078
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
The test cluster took slightly more than 10s to apply the cluster state for the mapping update randomly which failed the run in elastic#75941. This only ever failed once but since there's no real harm in doing so increasing the timeout to 30s here like we did in other similar spots. closes elastic#75941
original-brownbear
added
>test
elasticmachine
added
the
Team:Distributed (Obsolete)
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
Contributor
Author
|
Thanks Tanguy! |
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this pull request
Aug 4, 2021
The test cluster took slightly more than 10s to apply the cluster state for the mapping update randomly which failed the run in elastic#75941. This only ever failed once but since there's no real harm in doing so increasing the timeout to 30s here like we did in other similar spots. closes elastic#75941
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this pull request
Aug 4, 2021
The test cluster took slightly more than 10s to apply the cluster state for the mapping update randomly which failed the run in elastic#75941. This only ever failed once but since there's no real harm in doing so increasing the timeout to 30s here like we did in other similar spots. closes elastic#75941
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
The test cluster took slightly more than 10s to apply the cluster state for the mapping update
randomly which failed the run in #75941. This only ever failed once but since there's no real harm in doing so
increasing the timeout to 30s here like we did in other similar spots.
closes #75941