-
Notifications
You must be signed in to change notification settings - Fork 122
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
Throttle integration test fixes #696
Conversation
@@ -1236,6 +1236,8 @@ func (tr TestRun) waitForSlashThrottleDequeue( | |||
|
|||
time.Sleep(500 * time.Millisecond) | |||
} | |||
// Sleep 20 seconds to pass a block, allowing the jailing to be incorporated into voting power |
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.
@MSalopek depending on block time when running in the cloud, this may need to be adjusted
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.
LGTM!
Thanks for taking the time to look into this.
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.
LGTM
BTW I just tried running the same test with a longer replenish period, and longer timeout. The test still passes if the ie. with a replenish period of 20 seconds and a block time of 20 seconds, throttling will act no different than allowing a packet to be handled once per block. This is why #684 was not caught by integration tests |
Description
The diffs in #687 caused integration tests to fail, which is actually good and proves that the patch changed behavior. This PR fixes integration tests to be a bit more granular with the throttle behavior that's expected.
Type of change
Testing
: Adds testingNew Behavior Testing
Full integration tests pass locally for me,
make test-integration