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] RecoveryDuringReplicationTests.testResyncAfterPrimaryPromotion failing reproducibly #52598

Closed
mark-vieira opened this issue Feb 20, 2020 · 3 comments · Fixed by #52615
Closed
Assignees
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI

Comments

@mark-vieira
Copy link
Contributor

This test just failed and reproduces locally for me.

https://gradle-enterprise.elastic.co/s/lflqfnox2xl4c/tests/nfxodyych4uas-b7kbbqymo3ykc

    java.lang.AssertionError: 
    Expected: is <5>
         but: was <1>
        at __randomizedtesting.SeedInfo.seed([F5E9DF78AE4335DB:F82474D3A9A0FC1F]:0)
        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.index.replication.RecoveryDuringReplicationTests.testResyncAfterPrimaryPromotion(RecoveryDuringReplicationTests.java:380)
REPRODUCE WITH: ./gradlew ':server:test' --tests "org.elasticsearch.index.replication.RecoveryDuringReplicationTests.testResyncAfterPrimaryPromotion" -Dtests.seed=F5E9DF78AE4335DB -Dtests.security.manager=true -Dtests.locale=es-ES -Dtests.timezone=Europe/Uzhgorod -Dcompiler.java=13
@mark-vieira mark-vieira added >test-failure Triaged test failures from CI :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. labels Feb 20, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Recovery)

@mark-vieira
Copy link
Contributor Author

Given this reproduced for me locally we are certain to encounter this failure again so I've muted this test in master with 1d0e342.

@dnhatn dnhatn self-assigned this Feb 20, 2020
ywelsch pushed a commit that referenced this issue Feb 21, 2020
Adjusts the assertion as we might eagerly clean up translog during resync since #52556

Relates #52556
Closes #52598
@mark-vieira
Copy link
Contributor Author

Thanks, @ywelsch!

dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Feb 26, 2020
Adjusts the assertion as we might eagerly clean up translog during resync since elastic#52556

Relates elastic#52556
Closes elastic#52598
dnhatn added a commit that referenced this issue Feb 26, 2020
Adjusts the assertion as we might eagerly clean up translog during resync since #52556

Relates #52556
Closes #52598
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants