-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[AUTOCUT] Gradle Check Flaky Test Report for ApproximatePointRangeQueryTests #15807
Labels
autocut
flaky-test
Random test failure that succeeds on second run
>test-failure
Test failure from CI, local build, etc.
Comments
opensearch-ci-bot
added
>test-failure
Test failure from CI, local build, etc.
autocut
flaky-test
Random test failure that succeeds on second run
untriaged
labels
Sep 6, 2024
This should be fixed by #15590 |
Merged
3 tasks
3 tasks
inpink
added a commit
to inpink/OpenSearch
that referenced
this issue
Oct 22, 2024
…ing totalHits assertion logic (opensearch-project#15807) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. Signed-off-by: inpink <inpink@kakao.com>
inpink
added a commit
to inpink/OpenSearch
that referenced
this issue
Oct 23, 2024
…ing totalHits assertion logic (opensearch-project#15807) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. Signed-off-by: inpink <inpink@kakao.com>
inpink
added a commit
to inpink/OpenSearch
that referenced
this issue
Oct 23, 2024
…ing totalHits assertion logic (opensearch-project#15807) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. Signed-off-by: inpink <inpink@kakao.com>
dbwiddis
pushed a commit
that referenced
this issue
Oct 23, 2024
…ing totalHits assertion logic (#15807) (#16434) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. Signed-off-by: inpink <inpink@kakao.com>
opensearch-trigger-bot bot
pushed a commit
that referenced
this issue
Oct 23, 2024
…ing totalHits assertion logic (#15807) (#16434) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. Signed-off-by: inpink <inpink@kakao.com> (cherry picked from commit 66f0110) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dbwiddis
pushed a commit
that referenced
this issue
Oct 23, 2024
…ing totalHits assertion logic (#15807) (#16434) (#16459) - Updated the test to account for Lucene's behavior where `IndexSearcher.search()` may return `GREATER_THAN_OR_EQUAL_TO` for totalHits when the number of matches exceeds 1000. - Added logic to check if `totalHits.relation` is `EQUAL_TO`. If so, assert that the count is exactly 11000. Otherwise, ensure the count is at least 11000 and within the allowed upper limit (`maxHits`). - This change prevents intermittent test failures caused by Lucene’s performance optimizations. (cherry picked from commit 66f0110) Signed-off-by: inpink <inpink@kakao.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
autocut
flaky-test
Random test failure that succeeds on second run
>test-failure
Test failure from CI, local build, etc.
Flaky Test Report for
ApproximatePointRangeQueryTests
Noticed the
ApproximatePointRangeQueryTests
has some flaky, failing tests that failed during post-merge actions.Details
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeShortCircuit
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeUnderDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeUnderDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeUnderDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeShortCircuitAscSort
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeUnderDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeShortCircuit
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeShortCircuitAscSort
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeWithSizeOverDefault
org.opensearch.search.approximate.ApproximatePointRangeQueryTests.testApproximateRangeShortCircuit
The other pull requests, besides those involved in post-merge actions, that contain failing tests with the
ApproximatePointRangeQueryTests
class are:For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.
The text was updated successfully, but these errors were encountered: