-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: intermittent failure in feature_llmq_simplepose.py #5859
Conversation
878bd28
to
9b6eb25
Compare
@kwvg claims that with this patch it still fails randomly on his machine, but only 1/3 of failures compare to without patch.
vs
any ideas how we can improve this simplepose test futhermore? |
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 don't see any improvement on my machine using this PR. Nodes drop connections on develop
for no clear reason (no errors in logs). Simply waiting for connections did not help so I tried moving block generation out of the loop and suddenly d89f41c fixed the issue for me. But I don't understand how/why exactly... 🤷♂️ It would be nice if someone could explain why it worked 😄 Anyway, pls try this patch instead and share your thoughts.
almost fixed for me, still one failure out of 20 which is pretty good @kwvg , can you test it, please?
|
9b6eb25
to
ea0d064
Compare
|
I think I figured it out. Previously isolated nodes are trying to fetch blocks they missed as soon as they have a new connection open. When we bump mocktime 10+ minutes in the middle of that we trigger |
|
ea0d064
to
623c30d
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.
Pls check f8581d8
this one works perfectly for me.
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 :)
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.
utACK for squash merge
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.
post-merge utACK
Issue being fixed or feature implemented
kudos to kwvg to report issue: he pointed out that functional tests randomly fail lately.
Bisect pointed out an exact commit: bitcoin#20027 - mockable time everywhere
What was done?
Added call
mn.node.mockscheduler
as it is done in 20027 for other functional testsHow Has This Been Tested?
Run 20 times. Without this patch 20% failures; with this patch - zero failures.
Breaking Changes
N/a
Checklist: