-
Notifications
You must be signed in to change notification settings - Fork 931
merge queue: embarking unstable (538067f), #7717 and #7655 together #7732
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
* Clean up and add more code comments on BPO forks. * Fix tests. * Fix tests. * Fix moar tests. * Fix moar tests. * Ensure the same `ChainSpec` is used throughout the tests. * Refactor `ForkContext` to avoid recomputing fork digests and using cached values. * Fix failing tests due to mismatching chainspec and block slots. * Review comments - adjust code style and add docs. * make sure all forks are covered in tests --------- Co-authored-by: Pawan Dhananjay <[email protected]>
|
|
1 similar comment
|
|
🎉 This pull request has been checked successfully and will be merged soon. 🎉
Branch unstable (538067f), #7717 and #7655 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #7655.
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=local-testnet-successcheck-success=test-suite-successRequired conditions to stay in the queue:
#approved-reviews-by >= 1fusaka-devnet-2#7655check-success=license/clafusaka-devnet-2#7655check-success=target-branch-checkfusaka-devnet-2#7655label!=do-not-mergefusaka-devnet-2#7655