Parent Log: http://ci.aztec-labs.com/e11ece80e16ce810 Command: 6978e0e5f3e9e568 yarn-project/scripts/run_test.sh slasher/src/epoch_prune_watcher.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/db5c19349590089393771b38c3a27e7e65f736a6 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Mon Jun 23 17:23:15 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_b74a89389ab8b2c7_next 17:23:17 [17:23:17.804] INFO: epoch-prune-watcher EpochPruneWatcher initialized 17:23:18 [17:23:18.200] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 17:23:18 [17:23:18.206] INFO: epoch-prune-watcher Data for pruned epoch 1 was not available. Will want to slash. 17:23:18 err: { 17:23:18 "type": "TransactionsNotAvailableError", 17:23:18 "message": "Validator Error: Transactions not available: 0x2dcec0746237161d07eeee1319773489d3e4bb073a9b98958dc9379578ca45e8", 17:23:18 "stack": 17:23:18 Error: Validator Error: Transactions not available: 0x2dcec0746237161d07eeee1319773489d3e4bb073a9b98958dc9379578ca45e8 17:23:18 at EpochPruneWatcher.validateBlock (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:128:13) 17:23:18 at EpochPruneWatcher.validateBlocks (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:113:9) 17:23:18 } 17:23:18 [17:23:18.224] INFO: epoch-prune-watcher Slash for epoch 1 created. {"0":{"amount":1000000000000000000,"offense":1,"validator":"0x0000000000000000000000000000000000000abc"},"1":{"amount":1000000000000000000,"offense":1,"validator":"0x0000000000000000000000000000000000000def"}} 17:23:18 [17:23:18.237] INFO: epoch-prune-watcher EpochPruneWatcher initialized 17:23:18 [17:23:18.454] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 17:23:18 [17:23:18.455] INFO: epoch-prune-watcher Pruned epoch 1 was valid. Want to slash committee for not having it proven. 17:23:18 [17:23:18.456] INFO: epoch-prune-watcher Slash for epoch 1 created. {"0":{"amount":1000000000000000000,"offense":2,"validator":"0x0000000000000000000000000000000000000abc"},"1":{"amount":1000000000000000000,"offense":2,"validator":"0x0000000000000000000000000000000000000def"}} 17:23:18 [17:23:18.462] INFO: epoch-prune-watcher EpochPruneWatcher initialized 17:23:18 [17:23:18.542] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 17:23:18 [17:23:18.545] ERROR: epoch-prune-watcher Error while validating pruned epoch 1. Will not want to slash.: ReExStateMismatchError: Validator Error: Re-execution state mismatch 17:23:18 at EpochPruneWatcher.validateBlock (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:146:13) 17:23:18 at EpochPruneWatcher.validateBlocks (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:113:9) { 17:23:18 expectedArchiveRoot: Fr<0x0000000000000000000000000000000000000000000000000000000000000002>, 17:23:18 actualArchiveRoot: Fr<0x0000000000000000000000000000000000000000000000000000000000000003>, 17:23:18 expectedStateReference: undefined, 17:23:18 actualStateReference: undefined 17:23:18 } 17:23:18 PASS src/epoch_prune_watcher.test.ts 17:23:18 EpochPruneWatcher 17:23:18 should emit WANT_TO_SLASH_EVENT when a validator is in a pruned epoch when data is unavailable (433 ms) 17:23:18 should slash if the data is available and the epoch could have been proven (225 ms) 17:23:18 should not slash if the data is available but the epoch could not have been proven (85 ms) 17:23:18 17:23:18 Test Suites: 1 passed, 1 total 17:23:18 Tests: 3 passed, 3 total 17:23:18 Snapshots: 0 total 17:23:18 Time: 2.07 s 17:23:18 Ran all test suites matching slasher/src/epoch_prune_watcher.test.ts. 17:23:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?