-
Notifications
You must be signed in to change notification settings - Fork 957
merge queue: embarking unstable (d80c0ff) and #8075 together #8107
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
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
….com/jimmygchen/lighthouse into backfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
…m/eserilev/lighthouse into reconstruction-scoped-thread-pool
…construction-scoped-thread-pool
…m/eserilev/lighthouse into reconstruction-scoped-thread-pool
…construction-scoped-thread-pool
|
|
|
|
❌ This pull request has failed checks. #8075 will be removed from the queue. ❌
Branch unstable (d80c0ff) and #8075 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #8075.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
defaultfor merge:check-success=test-suite-successcheck-success=local-testnet-successRequired conditions to stay in the queue:
#approved-reviews-by >= 1check-success=license/clacheck-success=target-branch-checklabel!=do-not-merge