This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
[json-tests] stReturnDataTest blockchain test failures #11074
Labels
F4-tests 💻
Tests need fixing, improving or augmenting.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
After #11054 the following JSON tests fail in
stReturnDataTest/
and are added to the list of skipped tests inethcore/res/ethereum/tests-issues/currents.json
.Fix the tests and "un-skip" them.
Investigation
The issue here is about the genesis block not matching the test expectation. We end up with a genesis block with hash
0x3d3cd0c74d5040bd64c4077146499e075459c7facf999ebfcc2eac2bd81183e9
and the test block expects the parent hash to be0x43dd448195341d2b9ff0683061d5003dfdef21c9dd5f9132c71df9982664a2d2
and so the block import fails with anUnknownParent
error.The genesis block is constructed using the state from the
pre
section of the test file. Thestate_root
we calculate from this data,0x66bfe5cd9198e024259b887599af885c4f03ec4925b854ddf8525c60f404068c
, does not match what the test expects,0x7c3eb449ede11443a1e9d714c211702d5f6e73d0c41f5af8936f9567ffde1a0f
.This is likely what causes the genesis blocks
hash
to be wrong (indeed, thegenesisRLP
from the test file is identical tospec.genesis_block().to_hex()
except for thestate_root
).This is most likely the same bug as #11075.
As far as I can tell we deserialize the data properly from disk.
The text was updated successfully, but these errors were encountered: