Add retry mechanism to handle race conditions where ZMQ notifications aren’t immediately available after blockchain operations, preventing zmq.error.Again exceptions that cause test failures on slower systems.
Fixes #34189
Add retry mechanism to handle race conditions where ZMQ notifications
aren't immediately available after blockchain operations, preventing
zmq.error.Again exceptions that cause test failures on slower systems.
Fixes #34189
Signed-off-by: janhavi <janhavi@janhavis-MacBook-Air.local>
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process. A summary of reviews will appear here.
🚧 At least one of the CI tasks failed.
Task lint: https://github.com/bitcoin/bitcoin/actions/runs/21701878305/job/62834121764
LLM reason (✨ experimental): Lint failure: ruff detected Python lint errors (trailing whitespace) in the code.
Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:
Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.
A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.
An intermittent issue.
Leave a comment here, if you need help tracking down a confusing failure.
I’ll close this for now. Feel free to open a new pull, but make sure to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits
Also, you’ll have to address the lint CI failure.
There is no need to push new commits here without addressing any of the feedback.