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

org.elasticsearch.indices.recovery.IndexPrimaryRelocationIT » testPrimaryRelocationWhileIndexing fails on darwin #46526

Closed
atorok opened this issue Sep 10, 2019 · 1 comment · Fixed by #46554

Comments

@atorok
Copy link
Contributor

commented Sep 10, 2019

Example build failure

https://gradle-enterprise.elastic.co/s/gqfaatobjihsg/tests/kyv2y2z3r4v7m-k6caxamfw3ngk
https://gradle-enterprise.elastic.co/s/wxxigl7sdy7zy
https://gradle-enterprise.elastic.co/s/gqfaatobjihsg
https://gradle-enterprise.elastic.co/s/jm4xwpnnsezmo
https://gradle-enterprise.elastic.co/s/jm4xwpnnsezmo
https://gradle-enterprise.elastic.co/s/2qcg42go5eelu
https://gradle-enterprise.elastic.co/s/gxzq6jkffcook
https://gradle-enterprise.elastic.co/s/gxzq6jkffcook

All of them on darwin.

Reproduction line

./gradlew ':server:integTest' --tests "org.elasticsearch.indices.recovery.IndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing" -Dtests.seed=70AAB4CC91E51F92 -Dtests.security.manager=true -Dtests.locale=is -Dtests.timezone=Pacific/Port_Moresby -Dcompiler.java=12 -Druntime.java=11

Example relevant log:

java.lang.AssertionError: 

Expected: <false>
     but: was <true>
Close stacktrace
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.indices.recovery.IndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing(IndexPrimaryRelocationIT.java:84)
...
@elasticmachine

This comment has been minimized.

Copy link
Collaborator

commented Sep 10, 2019

atorok added a commit that referenced this issue Sep 10, 2019

@dnhatn dnhatn self-assigned this Sep 10, 2019

dnhatn added a commit that referenced this issue Sep 11, 2019
Increase timeout for relocation tests (#46554)
There's nothing wrong in the logs from these failures. I think 30
seconds might not be enough to relocate shards with many documents as CI
is quite slow. This change increases the timeout to 60 seconds for these
relocation tests. It also dumps the hot threads in case of timed out.

Closes #46526
Closes #46439
dnhatn added a commit that referenced this issue Sep 12, 2019
Increase timeout for relocation tests (#46554)
There's nothing wrong in the logs from these failures. I think 30
seconds might not be enough to relocate shards with many documents as CI
is quite slow. This change increases the timeout to 60 seconds for these
relocation tests. It also dumps the hot threads in case of timed out.

Closes #46526
Closes #46439
dnhatn added a commit that referenced this issue Sep 12, 2019
Increase timeout for relocation tests (#46554)
There's nothing wrong in the logs from these failures. I think 30
seconds might not be enough to relocate shards with many documents as CI
is quite slow. This change increases the timeout to 60 seconds for these
relocation tests. It also dumps the hot threads in case of timed out.

Closes #46526
Closes #46439
turackangal added a commit to turackangal/elasticsearch that referenced this issue Sep 14, 2019
turackangal added a commit to turackangal/elasticsearch that referenced this issue Sep 14, 2019
Increase timeout for relocation tests (elastic#46554)
There's nothing wrong in the logs from these failures. I think 30
seconds might not be enough to relocate shards with many documents as CI
is quite slow. This change increases the timeout to 60 seconds for these
relocation tests. It also dumps the hot threads in case of timed out.

Closes elastic#46526
Closes elastic#46439
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.