-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] testCoordinatingPrimaryThreadedUpdateToShardLimitsAndRejections is flaky #5157
Comments
This is a very similar test and failure as mentioned in #4212. I suspect the fix will be the same for both. I'm capturing the notes I've collected on this so far below: The test expects In theory, this close call should clean up everything being tracked and result in that assertion being true. The only suspect I have is that the close conditionally cleans up the stats being tracked. I suspect there may be a race preventing the values getting to zero tested in that condition. I haven't figured out how that might be possible though. I can get this to fail locally somewhat reliably. However, if it fails, it always seems to fail on the first attempt. If I run it many times the retries never seem to fail. This suggests to me it is some sort of race condition. |
Similar to falky test : #4212 , test only fails when rejectionCount is equal to NUM_THREADS. Possible fix/workaround would be similar to this comment. Need @getsaurabh02 opinion on this to move forward with fix. |
thanks @Rishikesh1159 . Could you pls check #4212 (comment) |
Closing this as #5439 is merged, which fixes the issue. Please feel free to reopen if this test fails again. |
Describe the bug
#5143
The text was updated successfully, but these errors were encountered: