The InvalidMissingAncestorReOrgSyncTest tests consistently fail with TEST ISSUE - Failed to set invalid block: missing trie node errors. This is apparently caused by the modified geth module using PathScheme for state storage, which has strict trie integrity requirements incompatible with inserting blocks containing invalid headers.
Error
TEST ISSUE - Failed to set invalid block: failed to commit state: commit aborted due to database error:
missing trie node bcce1472eb9dba20d7c6261be584a4f269252a86becefd17c0179c4a9daebdc2
(owner 37d65eaa92c6bc4c13a5ec45527f0c18ea8932588728769ec7aecfe6d9f32e42) (path ) unexpected node: ...
We saw that this test is failing in all clients with the same error, and could be verified in: https://hive.ethpandaops.io/#/group/generic (engine-cancun tests)
Quick fix
Modifying the DB schema to hash based instead solved the issue locally for ethrex, i could create a quick PR with the fix (changing rawdb.PathScheme to rawdb.HashScheme in node.go:184) but I'm not sure if its desirable to change the schema for all tests.
The
InvalidMissingAncestorReOrgSyncTesttests consistently fail with TEST ISSUE - Failed to set invalid block: missing trie node errors. This is apparently caused by the modified geth module using PathScheme for state storage, which has strict trie integrity requirements incompatible with inserting blocks containing invalid headers.Error
We saw that this test is failing in all clients with the same error, and could be verified in: https://hive.ethpandaops.io/#/group/generic (engine-cancun tests)
Quick fix
Modifying the DB schema to hash based instead solved the issue locally for ethrex, i could create a quick PR with the fix (changing rawdb.PathScheme to rawdb.HashScheme in node.go:184) but I'm not sure if its desirable to change the schema for all tests.