Conversation
|
@onbjerg one more thing i've noticed is that some bodies tests are flaky. |
Codecov Report
@@ Coverage Diff @@
## main #204 +/- ##
==========================================
- Coverage 67.74% 66.86% -0.88%
==========================================
Files 213 217 +4
Lines 18142 18205 +63
==========================================
- Hits 12290 12173 -117
- Misses 5852 6032 +180
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
This is likely because the blocks are randomly generated and empty blocks are skipped, i.e. if a block has no ommers and no transactions we don't request it from the network. So the amount of blocks processed by the stage might deviate a bit |
onbjerg
left a comment
There was a problem hiding this comment.
A few questions, but also unsure how to validate if the body tests do the same things as before/cover the same edge cases. Any ideas on how we could do that?
|
@onbjerg not sure other than the manual inspection. i removed the tests that are covered by the |
|
@rkrasiuk Seems like the same lines are covered in both stages, so should be good |
|
@gakonst yeah, for headers you need to update chain tip before await the value |
…e` (paradigmxyz#204) - Adds new crates `reth-optimism-exex` and `reth_optimism_trie` - Moves `reth_exex::external_proofs` -> `reth_optimism_exex` - Moves `reth_exex::external_proofs::storage` -> `reth_optimism_trie`
…e` (paradigmxyz#204) - Adds new crates `reth-optimism-exex` and `reth_optimism_trie` - Moves `reth_exex::external_proofs` -> `reth_optimism_exex` - Moves `reth_exex::external_proofs::storage` -> `reth_optimism_trie`
…e` (paradigmxyz#204) - Adds new crates `reth-optimism-exex` and `reth_optimism_trie` - Moves `reth_exex::external_proofs` -> `reth_optimism_exex` - Moves `reth_exex::external_proofs::storage` -> `reth_optimism_trie`
…e` (paradigmxyz#204) - Adds new crates `reth-optimism-exex` and `reth_optimism_trie` - Moves `reth_exex::external_proofs` -> `reth_optimism_exex` - Moves `reth_exex::external_proofs::storage` -> `reth_optimism_trie`
Create a common test suite for stages.
The
stage_test_suitemacro contains the default stage tests impl:Stage::executewith empty dbStage::executewith inputstage_progressequal toprev_stage_progressStage::executewith normal input and validate the database entriesStage::unwindwith empty dbStage::executeand callStage::unwindto the originalstage_progress. validate the database state after each call