-
Notifications
You must be signed in to change notification settings - Fork 211
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
Prefer waiting over eventually in migration tests #2700
Conversation
Our parameters must have changed since hard-coding the previous delay.
a95fb39
to
1f81db0
Compare
bors try |
tryBuild failed: #expected |
1f81db0
to
c302ef1
Compare
bors try |
tryBuild failed:
Mac |
bors try |
tryBuild failed:
|
bors try |
tryBuild failed:
|
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.
So the reason for this change is that between checking one wallet condition and the next, the chain rolls back and invalidates the first condition, such that the second condition fails?
Before making a solution, do we have logging which proves conclusively that this is the case?
And what about other ways to solve this? We need some methods to make our tests less fragile - otherwise this flakiness will keep on happening.
My two ideas so far are:
- Provide API endpoints to pause and resume syncing for a wallet - preventing rollback while assertions are being checked.
- Provide a way for assertions to be contingent on a certain TxId having status=InLedger. If an assertion fails, and the Tx has gone back to Pending, then restart the
eventually
block from the beginning.
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.
Why not
bors r+ |
Build succeeded: |
Issue Number
ADP-970, #2699
Overview
waitForTxImmutability
should now only need to be 10s instead of 16swaitForTxImmutability
instead ofeventually
to protect against rollbacks in migration testsComments
it
witheventually
, but we should moving away from the retrying it, not re-adding it.