Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
4134: Re-enable SN epoch integration test r=jordanschalm a=jordanschalm ## Context The test failure was caused by this fatal error from the Consensus Node brought up to join in the second epoch: `··· DOCK: 2023-03-30 19:48:34.635587 +0000 UTC (clogs ) consensus_test_3 (16726f0fad5781fa651f6a048c007e9f6a4202f8111811cbec685ac96774c32a) - �{"level":"fatal","node_role":"consensus","node_id":"522f1406e6e0c2267dbcc49519539c18d866a584df709e1a277bdbc28bd2d40c","error":"component sealing engine initialization failed: could not repopulate assignment collectors tree: internal error while traversing fork: visitor errored on block 6058fc1a85eaff3f46fe1d2a530ea7fe648cef771c75594bcfeef66238450bda at height 57: could not process incorporated result from block 6058fc1a85eaff3f46fe1d2a530ea7fe648cef771c75594bcfeef66238450bda: could not process incorporated incRes: could not process incorporated result 741f4ba4ad5ff7918b7aaa615306f136ae2e2b9b13a729e115e9fb48c2713b03: could not determine chunk assignment: failed to retrieve source of randomness: could not retrieve quorum certificate for (6058fc1a85eaff3f46fe1d2a530ea7fe648cef771c75594bcfeef66238450bda): could not retrieve resource: key not found","time":"2023-03-30T19:48:34.634479451Z","message":"unhandled irrecoverable error"}` The problem is that, the sealing engine attempts to populate its state using the sealing segment, but it cannot read the QC for some of these blocks. In #3947, we changed to read QCs from storage directly in all cases. However, these QCs were not stored in QC storage for all blocks, in particular sealing segment blocks. ## Changes - Fixes the bug by inserting QCs explicitly for all sealing segment blocks and adds a test case - Re-enables the integration test Co-authored-by: Jordan Schalm <jordan@dapperlabs.com>
- Loading branch information