-
Notifications
You must be signed in to change notification settings - Fork 235
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
Run all available ValidBlock
tests
#597
Conversation
Codecov ReportBase: 80.67% // Head: 80.84% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #597 +/- ##
==========================================
+ Coverage 80.67% 80.84% +0.17%
==========================================
Files 370 370
Lines 21648 20095 -1553
==========================================
- Hits 17464 16246 -1218
+ Misses 4184 3849 -335
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Is there a way of distinguishing between valid and invalid blocks, other that running them with Geth and seeing if they fail? If not, we should consider opening a bug upstream, since the tests should provide an expected result. |
Tracking upstream issue |
@SamWilsn @petertdavies Based on the response on the issue that I created on the ethereum tests repo, looks like these aren't necessarily tests with Invalid Blocks. Rather these include multi chain tests/re-orgs. Please see details. Do you think we should simply ignore these tests for specs since they might not be relevant? |
Tests involving reorgs are out of scope for us. Based on the names, I doubt the tests in |
Updated the valid block tests to ignore unrelated tests including |
492a701
to
2e7f79e
Compare
efc1a5a
to
0103050
Compare
tests passed locally. |
(closes #594 )
What was wrong?
Only a small sub-set of the
ValidBlock
test is currently being runRelated to Issue #594
How was it fixed?
Some of the
ValidBlock
have Invalid blocks in them. For each hard fork, the following steps were doneIndependently identify which tests have Invalid Blocks in them. This was done by using
geth
. A test for whichgeth
was unable to generate a valid evm trace is assumed to have an invalid blockRun separate category of tests -
test_valid_block_incorrect
for tests with invalid blocks andtest_valid_block_correct
for ones with only valid blocks.Identify and mark tests that are slow or use large memory.
Cute Animal Picture