Parent Log: http://ci.aztec-labs.com/a0a5ca8d8b3bb5c7 Command: f643ae060f517c84 yarn-project/scripts/run_test.sh slasher/src/epoch_prune_watcher.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be78cf2e908c8f2f34676d72c74c8b92a3f591d1 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Fri Jun 20 23:00:18 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 23:00:20 [23:00:20.884] INFO: epoch-prune-watcher EpochPruneWatcher initialized 23:00:21 [23:00:21.183] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 23:00:21 [23:00:21.185] INFO: epoch-prune-watcher Data for pruned epoch 1 was not available. Will want to slash. 23:00:21 err: { 23:00:21 "type": "TransactionsNotAvailableError", 23:00:21 "message": "Validator Error: Transactions not available: 0x2bc58d0c24cc95a91378d887cf87a28402d75a455156eaa43bfecd5aac95e366", 23:00:21 "stack": 23:00:21 Error: Validator Error: Transactions not available: 0x2bc58d0c24cc95a91378d887cf87a28402d75a455156eaa43bfecd5aac95e366 23:00:21 at EpochPruneWatcher.validateBlock (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:128:13) 23:00:21 at EpochPruneWatcher.validateBlocks (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:113:9) 23:00:21 } 23:00:21 [23:00:21.193] INFO: epoch-prune-watcher Slash for epoch 1 created. {"0":{"amount":1000000000000000000,"offense":1,"validator":"0x0000000000000000000000000000000000000abc"},"1":{"amount":1000000000000000000,"offense":1,"validator":"0x0000000000000000000000000000000000000def"}} 23:00:21 [23:00:21.200] INFO: epoch-prune-watcher EpochPruneWatcher initialized 23:00:21 [23:00:21.353] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 23:00:21 [23:00:21.356] INFO: epoch-prune-watcher Pruned epoch 1 was valid. Want to slash committee for not having it proven. 23:00:21 [23:00:21.356] INFO: epoch-prune-watcher Slash for epoch 1 created. {"0":{"amount":1000000000000000000,"offense":2,"validator":"0x0000000000000000000000000000000000000abc"},"1":{"amount":1000000000000000000,"offense":2,"validator":"0x0000000000000000000000000000000000000def"}} 23:00:21 [23:00:21.362] INFO: epoch-prune-watcher EpochPruneWatcher initialized 23:00:21 [23:00:21.456] INFO: epoch-prune-watcher Detected chain prune. Validating epoch 1 23:00:21 [23:00:21.457] ERROR: epoch-prune-watcher Error while validating pruned epoch 1. Will not want to slash.: ReExStateMismatchError: Validator Error: Re-execution state mismatch 23:00:21 at EpochPruneWatcher.validateBlock (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:146:13) 23:00:21 at EpochPruneWatcher.validateBlocks (/home/aztec-dev/aztec-packages/yarn-project/slasher/src/epoch_prune_watcher.ts:113:9) { 23:00:21 expectedArchiveRoot: Fr<0x0000000000000000000000000000000000000000000000000000000000000002>, 23:00:21 actualArchiveRoot: Fr<0x0000000000000000000000000000000000000000000000000000000000000003>, 23:00:21 expectedStateReference: undefined, 23:00:21 actualStateReference: undefined 23:00:21 } 23:00:21 PASS src/epoch_prune_watcher.test.ts 23:00:21 EpochPruneWatcher 23:00:21 ✓ should emit WANT_TO_SLASH_EVENT when a validator is in a pruned epoch when data is unavailable (317 ms) 23:00:21 ✓ should slash if the data is available and the epoch could have been proven (162 ms) 23:00:21 ✓ should not slash if the data is available but the epoch could not have been proven (97 ms) 23:00:21 23:00:21 Test Suites: 1 passed, 1 total 23:00:21 Tests: 3 passed, 3 total 23:00:21 Snapshots: 0 total 23:00:21 Time: 1.887 s 23:00:21 Ran all test suites matching slasher/src/epoch_prune_watcher.test.ts. 23:00:21 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?