-
Notifications
You must be signed in to change notification settings - Fork 108
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
Intermittent test panics in non_finalized_state::tests::prop::finalized_equals_pushed_genesis #6498
Comments
I think we're going to need a full backtrace with debug info to diagnose this issue. In CI, I can't see the calling functions, so I don't know what code is actually causing this test failure. |
Failed PR #6515: @mpguerra another test that is failing regularly and should be fixed so we can reliably merge PRs. |
We might be able to diagnose this issue by changing the panic to a test error, and then committing the proptest seed to our git repository. If it's a reproducible error that only happens with some test data, it will happen all the time once we commit the seed. If it's a timing issue, then it won't happen reliably with the seed. (But we'll still have learnt something.) |
Let's devote some cycles this sprint to figuring out what's going on here |
It's possible that the test doesn't wait long enough for the blocks to commit to the state. Or the blocks are actually invalid, so they get rejected, but we're not checking for block commit errors. |
Looks like a test bug, there won't be any blocks in the partial chain if |
@arya2 can you please add a size for this issue? |
Motivation
We're seeing some failures in the merge queue due to an unrelated test bug:
https://github.com/ZcashFoundation/zebra/actions/runs/4672510901/jobs/8274774308#step:14:3305
https://github.com/ZcashFoundation/zebra/actions/runs/4684761663/jobs/8301221723?pr=6496#step:14:2893
Analysis
This could be a test bug, or it could be revealing a possible panic in production.
We should check the code that's panicking to decide how important this issue is.
The text was updated successfully, but these errors were encountered: