-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix randomization in testPerformActionAttrsRequestFails #43304
Merged
gwbrown
merged 2 commits into
elastic:master
from
gwbrown:ilm/fix-randomization-in-allocation-test
Jun 18, 2019
Merged
Fix randomization in testPerformActionAttrsRequestFails #43304
gwbrown
merged 2 commits into
elastic:master
from
gwbrown:ilm/fix-randomization-in-allocation-test
Jun 18, 2019
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
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added
>non-issue
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
v8.0.0
v7.3.0
v6.8.2
v7.2.1
labels
Jun 17, 2019
Pinging @elastic/es-core-features |
The test failure is #43342 @elasticmachine update branch |
@elasticmachine update branch |
dakrone
approved these changes
Jun 18, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Gordon!
gwbrown
added a commit
to gwbrown/elasticsearch
that referenced
this pull request
Jun 18, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added a commit
to gwbrown/elasticsearch
that referenced
this pull request
Jun 18, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added a commit
to gwbrown/elasticsearch
that referenced
this pull request
Jun 18, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added a commit
that referenced
this pull request
Jun 19, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added a commit
that referenced
this pull request
Jun 19, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
gwbrown
added a commit
that referenced
this pull request
Jun 19, 2019
The randomization in this test would occasionally generate duplicate node attribute keys, causing spurious test failures. This commit adjusts the randomization to not generate duplicate keys and cleans up the data structure used to hold the generated keys.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>non-issue
v6.8.2
v7.2.1
v7.3.0
v8.0.0-alpha1
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 randomization in this test would occasionally generate duplicate
node attribute keys, causing spurious test failures. This commit adjusts
the randomization to not generate duplicate keys and cleans up the data
structure used to hold the generated keys.
Fixes #42932