Switch tests to release-profile from dev-profile #3180
Draft
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.
This PR configures CI to execute tests with
cargo test --release
and fixes the tests that break when running withrelease
profile.All failing tests fail due to
snarkVM
test-helpers generating a sample genesis block, which panics only when running inrelease
profile (The genesis block must contain exactly 1 ratification
, originated from https://github.com/AleoHQ/snarkVM/blob/mainnet-staging/ledger/block/src/header/genesis.rs#L24-L27). It might make sense to refactor theVM::genesis_beacon()
-based fix over tosnarkVM
test-helpers side.In general, tests should be run on as production-like build as possible, so if
snarkVM
runs its tests withdev
profile, at leastsnarkOS
should dorelease
tests for appropriate coverage.