-
Notifications
You must be signed in to change notification settings - Fork 25.2k
InternalEngineTests.testLookupSeqNoByIdInLucene fails on master #35823
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
Comments
Pinging @elastic/es-distributed |
We looked into it during test triage power hour. It does indeed reproduce, but doesn't fail anymore if the call to |
The test testLookupSeqNoByIdInLucene fails because it expects if any change should be visible after a flush. However, that flush might be ignored if the waitIfOngoing parameter is false (the default value), and there is an ongoing flush triggered after merge is running. Closes elastic#35823
The test testLookupSeqNoByIdInLucene fails because it expects if any change should be visible after a flush. However, that flush might be ignored if the waitIfOngoing parameter is false (the default value), and there is an ongoing flush triggered after merge is running. Closes #35823
The test testLookupSeqNoByIdInLucene fails because it expects if any change should be visible after a flush. However, that flush might be ignored if the waitIfOngoing parameter is false (the default value), and there is an ongoing flush triggered after merge is running. Closes #35823
The test testLookupSeqNoByIdInLucene fails because it expects if any change should be visible after a flush. However, that flush might be ignored if the waitIfOngoing parameter is false (the default value), and there is an ongoing flush triggered after merge is running. Closes #35823
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=centos/74/console
Reproduces, but only if you leave out the method name:
The text was updated successfully, but these errors were encountered: