-
Notifications
You must be signed in to change notification settings - Fork 25k
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] org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT test {p0=indices.stats/13_fields/*} randomly fails on CI #27146
Labels
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
v6.0.3
v6.2.0
v7.0.0-beta1
Comments
colings86
added
>test-failure
Triaged test failures from CI
v6.0.0
v6.1.0
v7.0.0
labels
Oct 27, 2017
@jpountz any ideas what could be going on here? Maybe this is Java 9 related as I have only seen this fail with Java 9 on CI? |
tlrx
added a commit
that referenced
this issue
Jan 17, 2018
MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146
I pushed 6256c33 so that the test now waits for all the shards to be active with no ongoing relocations, because I suspect that the search queries from the set up sections could hit some shards that are later relocated to another node, losing the field data or completion stats. |
tlrx
added a commit
that referenced
this issue
Jan 17, 2018
MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146
tlrx
added a commit
that referenced
this issue
Jan 17, 2018
MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146
tlrx
added a commit
that referenced
this issue
Jan 17, 2018
MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146
tlrx
added a commit
that referenced
this issue
Jan 17, 2018
MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
v6.0.3
v6.2.0
v7.0.0-beta1
Example Build URL: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+java9-periodic/1112/console
Reproduce command (I cannot reproduce this locally):
Failure stack trace:
The text was updated successfully, but these errors were encountered: