-
Notifications
You must be signed in to change notification settings - Fork 180
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
Khalil/1908 fix gossipsub integration test #5323
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5323 +/- ##
==========================================
+ Coverage 55.97% 55.98% +0.01%
==========================================
Files 1017 1017
Lines 98513 98513
==========================================
+ Hits 55145 55157 +12
+ Misses 39161 39148 -13
- Partials 4207 4208 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
can you add some context about what's going on in this PR to the description? |
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.
Except one minor test case addition, the rest looks good 👍
}) | ||
t.Run("gossipsub spam mitigation invalid prunes", func(t *testing.T) { | ||
testGossipSubSpamMitigationIntegration(t, p2pmsg.CtrlMsgPrune) | ||
}) |
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.
Please also extend this test to iHave
as well. Effectively, unknown, malformed and duplicate topics for iHave
messages are also subsumed as spam attacks.
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.
This PR resolves the intermittent issues observed in the TestGossipSubSpamMitigationIntegration. To enhance the stability of the test, the following improvements have been made:
Test Case Splitting:
The test has been divided into two distinct test cases, focusing on graft and prune control message types separately. This allows for more granular analysis and troubleshooting.
Control Message Volume Adjustment:
The volume of control messages sent during the test has been increased. This adjustment ensures that the penalized score is sustained for a longer duration than the time it takes for the score to decay. This modification guarantees the completion of the test within a reasonable timeframe.