Closed adria0 closed 5 months ago
Attention: Patch coverage is 80.00000%
with 12 lines
in your changes missing coverage. Please review.
Project coverage is 82.08%. Comparing base (
80e69b9
) to head (a309ab1
). Report is 1 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
halo2_debug/src/lib.rs | 65.21% | 8 Missing :warning: |
halo2_backend/src/poly/ipa/commitment.rs | 77.77% | 2 Missing :warning: |
halo2_backend/src/poly/kzg/commitment.rs | 71.42% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
15,756 lines diff is a lot of lines to review!
Maybe you can remove halo2_proofs/dhat-heap.json
:P
15,756 lines diff is a lot of lines to review! Maybe you can remove
halo2_proofs/dhat-heap.json
:P
what a fancy PR! let's me remove it.
update: removed in ed4c33b
I have a doubt about the scope of the PR. This PR intend makes the tests deterministic, but does it intend to make the proof generation deterministic too? 🤔 I like the idea of having the random input of tests determined by a fixed seed, so that the tests can be easily reproduced. However, having the same mechanism for the random values of the protocol, like the blinders, may be a security issue. What is the idea for this type of randomness? @adria0 @ed255
Also, this is not related to determinitic tests, so I remove it, rethink, and make a future PR, if needed.
@ed255 @davidnevadoc I'll be rolling back some changes and I prefer to replace this PR to keep clean history again.
Make tests deterministic
halo2_debug
with some utilities, it can be reused for https://github.com/privacy-scaling-explorations/halo2/issues/343rand_chacha
for seeded randomness.cargo test
in M3 as also in coverage, creating crashes (since it's already activated). Also remove the associatedheap-profining
feature (that is activated with--all-features
)