-
Notifications
You must be signed in to change notification settings - Fork 547
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
[berkeley] Use Proof_cache for more transaction snark tests, make tests deterministic #14358
Conversation
!ci-build-me |
@@ -993,4 +1011,11 @@ let%test_module "Account precondition tests" = | |||
failwith | |||
"Expected transaction to fail due to invalid account \ | |||
precondition in the fee payer" ) ) | |||
|
|||
let () = | |||
match Sys.getenv_opt "PROOF_CACHE_OUT" with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens here if we run unit tests with -only-test
flags? Would we get a proof cache out at the end which is missing some of the necessary proofs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only if you also set the PROOF_CACHE_OUT
environment variable (see here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So basically: don't do that :)
!ci-build-me |
!approved-for-mainnet |
This PR builds upon #14031, using the
Proof_cache
mechanism to cache more proofs generated in the transaction snark tests.In order for this to work, this PR also replaces some uses of the non-deterministic
Private_key.create
with thePrivate_key.gen
quickcheck generator, so that we achieve cache hits for all of the relevant tests.Checklist: