Fix flaky SVS tiered flow test by removing incorrect flat buffer assertion#934
Open
Fix flaky SVS tiered flow test by removing incorrect flat buffer assertion#934
Conversation
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #934 +/- ##
=======================================
Coverage 96.99% 96.99%
=======================================
Files 129 129
Lines 7576 7576
=======================================
Hits 7348 7348
Misses 228 228 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove an incorrect assertion in
search_insertthat checkedget_curr_bf_size() == 0immediately afterwait_for_index(1).The flat buffer is not guaranteed to be empty at that point: vectors added during the current update job — but not enough to trigger another one — may still reside in the buffer. This caused flaky test failures.
Mark if applicable