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] CloseWhileRelocatingShardsIT.testCloseWhileRelocatingShards #37274

Closed
alpar-t opened this issue Jan 9, 2019 · 6 comments · Fixed by #37348
Closed

[CI] CloseWhileRelocatingShardsIT.testCloseWhileRelocatingShards #37274

alpar-t opened this issue Jan 9, 2019 · 6 comments · Fixed by #37348
Assignees
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >test-failure Triaged test failures from CI v7.0.0-beta1

Comments

@alpar-t
Copy link
Contributor

alpar-t commented Jan 9, 2019

Example build failure

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1156/console

Reproduction line

does reproduce locally

./gradlew :server:integTest \
  -Dtests.seed=ECD17CF0692217A \
  -Dtests.class=org.elasticsearch.indices.state.CloseWhileRelocatingShardsIT \
  -Dtests.method="testCloseWhileRelocatingShards" \
  -Dtests.security.manager=true \
  -Dtests.locale=en-US \
  -Dtests.timezone=Asia/Famagusta \
  -Dcompiler.java=11 \
  -Druntime.java=8

Example relevant log:

19:48:36    > Throwable #1: java.lang.AssertionError: Consider that the test failed if no indices were successfully closed
19:48:36    > Expected: a value greater than <0>
19:48:36    >      but: <0> was equal to <0>
19:48:36    > 	at __randomizedtesting.SeedInfo.seed([ECD17CF0692217A:2146095A290C77C0]:0)
19:48:36    > 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
19:48:36    > 	at org.elasticsearch.indices.state.CloseWhileRelocatingShardsIT.testCloseWhileRelocatingShards(CloseWhileRelocatingShardsIT.java:185)
19:48:36    > 	at java.lang.Thread.run(Thread.java:748)

Frequency

first of it's kind, "lucky" seed.

@alpar-t alpar-t added >test-failure Triaged test failures from CI v7.0.0 :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) labels Jan 9, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@alpar-t
Copy link
Contributor Author

alpar-t commented Jan 9, 2019

/cc @tlrx

@ywelsch ywelsch self-assigned this Jan 10, 2019
@ywelsch
Copy link
Contributor

ywelsch commented Jan 10, 2019

I've looked into this one and whether it could be caused by timeouts which we've been more frequently seeing on CI these days. That's not the case here, and rather looks to be an actual bug. Can you have a look @tlrx?

@ywelsch ywelsch assigned tlrx and unassigned ywelsch Jan 10, 2019
@alpar-t
Copy link
Contributor Author

alpar-t commented Jan 11, 2019

@tlrx
Copy link
Member

tlrx commented Jan 11, 2019

@atorok Thanks for the mute. I opened #37348 to fix the test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >test-failure Triaged test failures from CI v7.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants