-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix flaky test due to incorrect use of SSDV.nextOrd() #17626
Fix flaky test due to incorrect use of SSDV.nextOrd() #17626
Conversation
Signed-off-by: Rishabh Maurya <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17626 +/- ##
============================================
+ Coverage 72.46% 72.78% +0.31%
- Complexity 65757 66077 +320
============================================
Files 5311 5311
Lines 305001 305001
Branches 44230 44230
============================================
+ Hits 221022 221990 +968
+ Misses 65932 65187 -745
+ Partials 18047 17824 -223 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The copy-issue-labels workflow seems to be stuck? I'm going to close and re-open and see if that fixes things... |
❕ Gradle check result for 4399fef: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Description
Lucene 10 makes it illegal to call
SortedSetDocValues#nextOrd()
more than#docValueCount() times for the currently-positioned doc. This was causing flakiness inMultiOrdinalsTests
as encountered in PR #17446 with failure https://build.ci.opensearch.org/job/gradle-check/54686/testReport/junit/org.opensearch.index.fielddata.ordinals/MultiOrdinalsTests/testRandomValues/https://github.com/apache/lucene/blob/e7f9bc837e419672d9bfc829d01e643df667e9d4/lucene/core/src/java/org/apache/lucene/index/SortedSetDocValues.java#L36
We need to address this throughout the codebase thus created #17628
Related Issues
#17628
Check List
- [ ] API changes companion pull request created, if applicable.- [ ] Public documentation issue/PR created, if applicable.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.