-
Notifications
You must be signed in to change notification settings - Fork 893
merge queue: embarking unstable (cafb364) and #7816 together #7842
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
Conversation
commit 52bc831 Author: Michael Sproul <[email protected]> Date: Mon Jul 21 13:56:44 2025 +1000 Remove tracing instrumentation # Conflicts: # beacon_node/network/src/sync/manager.rs # beacon_node/network/src/sync/peer_sampling.rs
… into tracing-spans-test
…tly impacting component processing traces
# Conflicts: # beacon_node/beacon_chain/src/data_availability_checker/overflow_lru_cache.rs # beacon_node/beacon_chain/src/fetch_blobs/mod.rs # beacon_node/lighthouse_network/src/service/mod.rs
|
1 similar comment
|
❌ This pull request has failed checks. #7816 will be removed from the queue. ❌
Branch unstable (cafb364) and #7816 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #7816.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
default
for merge:check-success=test-suite-success
check-success=local-testnet-success
Required conditions to stay in the queue:
#approved-reviews-by >= 1
check-success=license/cla
check-success=target-branch-check
label!=do-not-merge