-
Notifications
You must be signed in to change notification settings - Fork 696
Fix: flaky net::tests::convergence
tests
#6046
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
Conversation
I made this change based on seeing peers being dropped in the logs with the reason, "the peer’s org dominates our peer table.” |
Hmm... based on that CI failure, it seems that this is not the problem here. |
In local and in my CI, those tests failed (with While One thing I couldn't do was running the tests as a group and not one by one in CI (I could do it in local tho). I catched those failures: For
Failures are often preceded by:
While for
Failures are often preceded by:
|
This was one cause of flaky `net::tests::convergence` tests.
This was another cause of flakiness in `net::tests::convergence` tests.
3c4e1e9
to
80f5cca
Compare
Updated with what I think is the correct fix (2 fixes actually).
|
Noice. LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
d4507ee
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6046 +/- ##
===========================================
+ Coverage 77.95% 83.45% +5.50%
===========================================
Files 538 538
Lines 387064 387015 -49
Branches 323 323
===========================================
+ Hits 301730 322985 +21255
+ Misses 85326 64022 -21304
Partials 8 8
... and 219 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Description
If my read of these tests is correct, we are just looking for convergence, and these tests should not be testing the pruning of neighbors, so it is best to set these soft max values to be the same as the total number of peers to avoid any non-deterministic pruning. The pruning should be tested elsewhere.See later comments and fixes.Applicable issues
net::tests::convergence::test_walk_star_15_plain
#5780