Skip to content
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

Closed
colings86 opened this issue Oct 27, 2017 · 2 comments
Assignees
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
Copy link
Contributor

Example Build URL: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+java9-periodic/1112/console

Reproduce command (I cannot reproduce this locally):

gradle :qa:mixed-cluster:v5.6.4-SNAPSHOT#mixedClusterTestRunner \
  -Dtests.seed=9094F5306A9A5286 \
  -Dtests.class=org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT \
  -Dtests.method="test {p0=indices.stats/13_fields/Fields - blank}" \
  -Dtests.security.manager=true \
  -Dtests.jvm.argline="--add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.nio.file=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.locks=ALL-UNNAMED --add-opens=java.base/java.util.regex=ALL-UNNAMED" \
  -Dtests.locale=ki \
  -Dtests.timezone=Etc/GMT+8

Failure stack trace:

<span class="timestamp"><b>12:35:47</b> </span>FAILURE 2.48s | MixedClusterClientYamlTestSuiteIT.test {p0=indices.stats/13_fields/Fields - blank} &lt;&lt;&lt; FAILURES!
<span class="timestamp"><b>12:35:47</b> </span>   &gt; Throwable #1: java.lang.AssertionError: Failure at [indices.stats/13_fields:72]: field [_all.total.fielddata.memory_size_in_bytes] is not greater than [0]
<span class="timestamp"><b>12:35:47</b> </span>   &gt; Expected: a value greater than &lt;0&gt;
<span class="timestamp"><b>12:35:47</b> </span>   &gt;      but: &lt;0&gt; was equal to &lt;0&gt;
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at __randomizedtesting.SeedInfo.seed([9094F5306A9A5286:18C0CAEAC4663F7E]:0)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:349)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:329)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at java.base/java.lang.Thread.run(Thread.java:844)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; Caused by: java.lang.AssertionError: field [_all.total.fielddata.memory_size_in_bytes] is not greater than [0]
<span class="timestamp"><b>12:35:47</b> </span>   &gt; Expected: a value greater than &lt;0&gt;
<span class="timestamp"><b>12:35:47</b> </span>   &gt;      but: &lt;0&gt; was equal to &lt;0&gt;
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.elasticsearch.test.rest.yaml.section.GreaterThanAssertion.doAssert(GreaterThanAssertion.java:65)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.elasticsearch.test.rest.yaml.section.Assertion.execute(Assertion.java:76)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:345)
<span class="timestamp"><b>12:35:47</b> </span>   &gt; 	... 37 more
@colings86 colings86 added >test-failure Triaged test failures from CI v6.0.0 v6.1.0 v7.0.0 labels Oct 27, 2017
@colings86
Copy link
Contributor Author

colings86 commented 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?

@lcawl lcawl added v6.0.1 and removed v6.0.0 labels Nov 13, 2017
@jaymode jaymode added v6.0.3 and removed v6.0.2 labels Dec 13, 2017
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
Copy link
Member

tlrx commented Jan 17, 2018

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 tlrx closed this as completed Jan 17, 2018
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
@colings86 colings86 added the >test Issues or PRs that are addressing/adding tests label Jan 22, 2018
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
Projects
None yet
Development

No branches or pull requests

5 participants