Open zhangchiqing opened 5 days ago
Attention: Patch coverage is 3.82979%
with 226 lines
in your changes missing coverage. Please review.
Project coverage is 41.18%. Comparing base (
ed149a7
) to head (6453fb4
). Report is 99 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
Working towards https://github.com/onflow/flow-go/issues/6557
This PR implemented option 4 in the above issue.
It adds a util command
verify-execution-result
that takes execution node's data and verifies every single chunks for a range blocks.Since we would like to make sure future cadence versions are backward compatible. This util allows us to capture any backward compatibilities issue from either FVM or cadence related changes.
For instance, if cadence introduces a breaking change, then it will be caught by running this
verify-execution-result
with a latest snapshot of EN. The util can verify the last 1M blocks, and 1 of the chunk might fail caused by the breaking change.I have verified with the latest testnet snapshot, and it worked. It verified 200K blocks after 3 hours, roughly 18 blocks per sec. The memory needed is about 14G.
Future optimization can be done by parallelizing the verification.