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

[BUG] Flaky test org.opensearch.remotestore.RemoteStoreIT.testRemoteStoreRestoreFromRemoteSegmentStore #6248

Closed
reta opened this issue Feb 8, 2023 · 8 comments
Labels
bug Something isn't working flaky-test Random test failure that succeeds on second run

Comments

@reta
Copy link
Collaborator

reta commented Feb 8, 2023

Describe the bug

The org.opensearch.remotestore.RemoteStoreIT.testRemoteStoreRestoreFromRemoteSegmentStore introduced by #6067 is flaky:

Error Message

java.lang.AssertionError: expected:<1> but was:<0>

Stacktrace

java.lang.AssertionError: expected:<1> but was:<0>
	at __randomizedtesting.SeedInfo.seed([D373B52E9B8323E0:848F02BF30313B1F]:0)
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:633)
	at org.opensearch.remotestore.RemoteStoreIT.verifyRestoredData(RemoteStoreIT.java:148)
	at org.opensearch.remotestore.RemoteStoreIT.testRemoteStoreRestoreFromRemoteSegmentStore(RemoteStoreIT.java:167)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)

To Reproduce
https://build.ci.opensearch.org/job/gradle-check/10883/

Expected behavior
Test should pass all the time

Plugins
Standard

Screenshots
N/A

Host/Environment (please complete the following information):

  • CI

Additional context
Add any other context about the problem here.

@reta reta added bug Something isn't working untriaged flaky-test Random test failure that succeeds on second run and removed untriaged labels Feb 8, 2023
@reta
Copy link
Collaborator Author

reta commented Feb 8, 2023

@sachinpkale this is another flaky one :( after #6067

@sachinpkale
Copy link
Member

:( Checking, I don't think it is due to #6067 but will check and fix.

@reta
Copy link
Collaborator Author

reta commented Feb 9, 2023

@sachinpkale
Copy link
Member

Yes, that is correct. I got confused with the PRs. I thought you were referring to latest changes to this test as per #6230.

@reta I have fixed the test in #6252. Please take a look.

@sachinpkale
Copy link
Member

Fixed in #6252

@dreamer-89
Copy link
Member

@sachinpkale : Can you please backport the fix to 2.x branch as well ? Found one occurrence #6288

@sachinpkale
Copy link
Member

This should be already backported. If it is still failing, I will mute the test.

@sachinpkale sachinpkale reopened this Feb 11, 2023
@sachinpkale
Copy link
Member

Not able to reproduce it with the same seed. Also, this is a different issue than the one mentioned in this ticket as the error is different. I am closing this ticket and opening new one. Muting the test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flaky-test Random test failure that succeeds on second run
Projects
None yet
Development

No branches or pull requests

3 participants