-
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
Few fixes for wait_for_instantlock
#3123
Conversation
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
Needs rebase. EDIT: #3124 is merged as well now. |
…red, use `wait_until` Currently it simply returns False if islock failed but that's not the way we use it (we never check results).
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
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
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-utACK
* Fix `wait_for_instantlock` to make it fail if instantlock wasn't aquired, use `wait_until` Currently it simply returns False if islock failed but that's not the way we use it (we never check results). * Wait for txes to propagate before checking for instantlock
Pls see individual commits for details.
Note:
p2p-instantsend.py
is expected to fail randomly now because of propagation issues which were not caught previously (should be fixed via #3124).Note2: Also needs #3122 to be merged first to importincluded similar changes herewait_until
, will rebase