Skip to content
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

main branch CI failed: push in Run tests #8976

Open
github-actions bot opened this issue Oct 25, 2024 · 1 comment
Open

main branch CI failed: push in Run tests #8976

github-actions bot opened this issue Oct 25, 2024 · 1 comment
Labels
S-ci-fail-auto-issue Status: Auto opened issue for a CI failure. This label is auto-assigned.

Comments

@github-actions
Copy link

GitHub Actions workflow Run tests #879 failed.

Event: push
Branch: main
Commit: f45f6f282c7b1b3e82594de328a2d4f1849bc99a

Created by jayqi/failed-build-issue-action

@github-actions github-actions bot added the S-ci-fail-auto-issue Status: Auto opened issue for a CI failure. This label is auto-assigned. label Oct 25, 2024
@github-project-automation github-project-automation bot moved this to New in Zebra Oct 25, 2024
@arya2
Copy link
Contributor

arya2 commented Oct 29, 2024

The stop_regex for this test ("stopping at configured height") was logged before "enabling mempool for debugging" and "activating mempool". The mempool is enabled on the first call to its poll_ready() method after Zebra syncs the genesis block, but it looks like Zebra reached the debug_stop_at_height of 400 before that.

The mempool is polled every 5 seconds by a QueueChecker task, and the syncer doesn't start looking for blocks to download until after the genesis block has been committed, so this should be very rare already, it had to have queried the network for blocks, downloaded them, verified them, and committed them, in less than 5 seconds*. Still, we could make practically impossible by repeatedly calling the get_raw_mempool() RPC method just in case.

*It's also possible that tokio was starving and delayed in waking up the queue checker. Very unusual conditions in any case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-ci-fail-auto-issue Status: Auto opened issue for a CI failure. This label is auto-assigned.
Projects
Status: New
Development

No branches or pull requests

1 participant