-
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
[CI] ClientYamlTestSuiteIT test {yaml=search/350_point_in_time/point-in-time with slicing} failing #75212
Labels
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
>test-failure
Triaged test failures from CI
Comments
iverase
added
:Search/Search
Search-related issues that do not fall into other categories
>test-failure
Triaged test failures from CI
labels
Jul 12, 2021
Pinging @elastic/es-search (Team:Search) |
I'm going to mute this one as it fails consistently and stops PRs from getting green. |
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 12, 2021
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 12, 2021
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 12, 2021
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 12, 2021
jtibshirani
added a commit
that referenced
this issue
Jul 14, 2021
Since the index may have more than one shard, we can't always predict how many documents will fall in each slice. This PR simply removes the checks, since we already test the slicing logic extensively in an integration test. The REST test is now just a sanity check for the API. Fixes #75212.
masseyke
pushed a commit
to masseyke/elasticsearch
that referenced
this issue
Jul 16, 2021
Since the index may have more than one shard, we can't always predict how many documents will fall in each slice. This PR simply removes the checks, since we already test the slicing logic extensively in an integration test. The REST test is now just a sanity check for the API. Fixes elastic#75212.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
>test-failure
Triaged test failures from CI
Only tried to reproduce in master
Build scan:
https://gradle-enterprise.elastic.co/s/c6ma6uoegmqvc/tests/:rest-api-spec:yamlRestCompatTest/org.elasticsearch.test.rest.ClientYamlTestSuiteIT/test%20%7Byaml=search%2F350_point_in_time%2Fpoint-in-time%20with%20slicing%7D
Reproduction line:
./gradlew ':rest-api-spec:yamlRestCompatTest' --tests "org.elasticsearch.test.rest.ClientYamlTestSuiteIT.test {yaml=search/350_point_in_time/point-in-time with slicing}" -Dtests.seed=EFB855388B8CF833 -Dtests.locale=pt-BR -Dtests.timezone=Asia/Pyongyang -Druntime.java=11
Applicable branches:
master
Reproduces locally?:
Yes
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.test.rest.ClientYamlTestSuiteIT&tests.test=test%20%7Byaml%3Dsearch/350_point_in_time/point-in-time%20with%20slicing%7D
Failure excerpt:
The text was updated successfully, but these errors were encountered: