[Tests] Fix skip version in yaml test for range fields in query_string #27878
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
cbuescher
added
>test-failure
jasontedor
reviewed
Dec 18, 2017
Member
jasontedor
left a comment
jasontedor
left a comment
There was a problem hiding this comment.
I left one comment about the version.
Member
There was a problem hiding this comment.
I think this should be " - 6.0.99"? It looks like the feature is in >= 6.1.0, not > 6.1.0?
cbuescher
force-pushed
the
fix-skipversion-6x
branch
from
9a2a236 to
a6ce7d0
Compare
Member
Author
|
@jasontedor thanks, I pushed a corrected version |
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.
The mixed cluster test on 6.x are currently failing on
range/10_basicrest tests becausethey are testing the use of range fields in query_string queries in a mixed cluster with 5.6 nodes.
According to #26552 this feature was only merged to version > 6.1.0
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/878/
This change moves the test causing these failures to their own test section that can be skipped for versions before 6.1.0