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
qa: Non-deterministic behavior in walletnotify.py #3464
Comments
I've experienced this multiple times over the past few weeks 😿 most recently https://github.com/xanimo/dogecoin/actions/runs/8547684076/job/23422183133 so +1 |
I picked through this a bit, and wanted to mention that the latest one-off CI failure for From #3514 Failed test log: https://github.com/dogecoin/dogecoin/actions/runs/8618664633/job/23621563836
|
The 40% failure rate wasn't a joke - I'm manually restarting nearly half the CI runs. Line 175 is the other place where we're testing notifications post-reorg, just like line 118. The first fail condition happens in the sunny case where the same tx gets mined post-reorg and the second fail condition happens in the rainy case where we get doublespent after a reorg. I'll put fixing this higher on my list. |
There seems to be non-deterministic behavior in
walletnotify.py
(or inCWallet::AddToWallet
) where 30-40% of the time, perhaps only under load, CI fails, always when testing notifications after reorgs.The text was updated successfully, but these errors were encountered: