-
Couldn't load subscription status.
- Fork 583
[Berkeley] develop #15423
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
Closed
[Berkeley] develop #15423
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…iner images change
Retry fork config export on empty or null response
Problem: fork config export requires stop-tx-slot to be at depth less than `k`. Solution: bump `k` and shorten window between stop-tx-slot and stop-chain-slot.
Plus fix checking emptiness check for blocks created after slot-chain-end
This commit moves script files and introduces a script that builds necessary dependencies and can be used both locally and from CI. Additionally, a CI job is introduced to executed the HF unit test as part of nightlies.
Nix image that is distributed on dockerhub doesn't have the latest nixpkgs. In particular it uses nixpkgs that doesn't fully support `?submodules=1` in flakes (case of submodules having submodules of their own, which triggered certain issues when building `compatible` branch).
When CI provides the necessary secret env variables (or they are provided locally), cache is updated with built binaries. This makes sure that repretetive runs do not need to rebuild binaries. But the most useful use case is that if `compatible` branch is updated rarely, it will not be rebuilt between updates, reducing the runtime of test by a few minutes at least.
This ensures that the test is randomized between runs, while allowing CI or user to specify the value that needs to be tested.
Implement checks for all ledger hashes that are used for generation of runtime config for the fork network. Solution continuously queries local network to capture last block of every epoch. These blocks contain snarked ledger hashes that will later (with the delay of 2 epochs) be used as staking/next ledgers. Then fork config is checked to contain the correct seeds (which are also in scope of this PR). This PR contains local patch against compatible to port runtime_genesis_ledger from berkeley (without sha3 hashing). This utility is to be executed after pre-fork network is stopped to generate hashes file using hashes of `compatible`. Then resulting hashes are compared against prevously captured snarked ledgers (in edge case, staking/next epoch ledgers of genesis epoch). This ensures fork config export (that is executed after slot_chain_end) reports correct ledgers.
…rotocol/mina into verify-ledger-hash-after-migration
This reverts commit cf4f6c4.
…rotocol/mina into verify-ledger-hash-after-migration
…rsion' into dkijania/separate_berkeley_migration_package
…we need to determine toolchain not based on profile. I introduce custom toolchain selection
Hard fork localnet test
…ission-for-verification-key-version make replayer --migration-mode to overwrite the versions
Add blockchain vk
…ompatible' into dkijania/port_guardian_script_to_berk
…ript_to_berk Port missing-blocks-guardian and include it into deb pkg to berk
…ania/port_mina_maintenance_docker_berk
…nance_docker_berk Port mina maintenance docker berk
…y_migration_package Reverting CI code to build sperate debian exclusively for berkeley migration package
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.