-
Notifications
You must be signed in to change notification settings - Fork 38.6k
test: Avoid intermittent test failure in feature_csv_activation.py #22907
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
|
Larger excerpt: |
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
Concept ACK |
|
It would make sense to separate the styling changes from the behavior change into separate commits. Concept ACK |
|
Makes sense. Done. |
fad5cb0 to
fa676db
Compare
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.
tAck fa676db
peertimeout will fix the test failure for now as it overrides the default timeout of 60 seconds
Tested on Ubuntu 21.02
fanquake
left a comment
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.
ACK fa676db
| self.num_nodes = 1 | ||
| self.setup_clean_chain = True | ||
| self.extra_args = [[ | ||
| '-peertimeout=999999', # bump because mocktime might cause a disconnect otherwise |
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.
I take it this needs to be an even larger timeout than we currently use in a few other places, i.e: "-peertimeout=9999", # bump because mocktime might cause a disconnect otherwise? Otherwise would be good to settle on the same LARGE number everywhere.
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.
It only needs to be 1 second longer than the whole duration of the test. If the test takes 100 seconds, it needs to be 101. So 9999 seems enough for our purposes here.
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.
Maybe peertimeout should be set to ~infinity by default in our functional tests, unless opted out?
…_csv_activation.py fa676db test: pep-8 whitespace (MarcoFalke) faed284 test: Avoid intermittent test failure in feature_csv_activation.py (MarcoFalke) Pull request description: Otherwise there will be disconnects if the test runs longer than the default peertimeout (60s): ``` node0 2021-09-05T20:28:30.973116Z (mocktime: 2021-09-01T07:17:29Z) [net] [net.cpp:1323] [InactivityCheck] socket receive timeout: 393061s peer=0 ``` Fix that by skipping `InactivityCheck` via a large `-peertimeout`. ACKs for top commit: fanquake: ACK fa676db Tree-SHA512: 061c0585a805aa2f8e55c4beedd4b8498a2951f33d60aa3632dda0a284db3a627d14a23dbd57e8a66c69a1612f39418e3a755c8ca97f6ae1105c0d70f0d1a801
Otherwise there will be disconnects if the test runs longer than the default peertimeout (60s):
Fix that by skipping
InactivityCheckvia a large-peertimeout.