-
Notifications
You must be signed in to change notification settings - Fork 679
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
Antithesis: Skip checks if tx confirmation fails #3563
Conversation
Are you looking to see this merged before or after the zap PR? |
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: marun <[email protected]>
I'm happy to rebase this on top of the zap PR |
) | ||
return | ||
} | ||
|
||
w.verifyXChainTxConsumedUTXOs(ctx, operationTx) |
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.
should this method be refactored to return an error? It seems to just log an error if one occurs during but then returns nothing.
I could create a follow up PR if so
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.
Because this function doesn't actually perform any modifications, it isn't required to propagate the error up... So that's why I didn't include that in this PR... But it certainly could.
Why this should be merged
The Antithesis tests have been consistently failing because the workload incorrectly skips transaction confirmation.
Specifically:
Errors this PR should resolve:
failed to verify that X-chain UTXO was deleted
failed to verify that P-chain UTXO was deleted
How this works
If the transaction confirmation check is cancelled, we do not perform verification of the expected state transition.
How this was tested
Ran locally and didn't see any regressions.
Need to be documented in RELEASES.md?
No.