Parent Log: http://ci.aztec-labs.com/3def59c4542ba0a9 Command: 2a84f19e72ab8189:ISOLATE=1:NAME=prover-node/src/prover-node.test.ts yarn-project/scripts/run_test.sh prover-node/src/prover-node.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/69efc9daf98e823f486416900de52fe8a44f25d9 Env: REF_NAME=gh-readonly-queue/next/pr-15187-6e2f55a89973b55c8c3c210b7f3a692b4d3d6473 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 23 16:07:30 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15187_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_next 16:07:30 +++ id -u 16:07:30 +++ id -g 16:07:30 ++ docker run -d --name prover-node_src_prover-node.test.ts --net=none --cpuset-cpus=0-127 --cpus=2 --memory=8g --user 1000:1000 -v/home/aztec-dev:/home/aztec-dev --mount type=tmpfs,target=/tmp,tmpfs-size=1g --workdir /home/aztec-dev/aztec-packages -e HOME -e VERBOSE -e GIT_CONFIG_GLOBAL=/home/aztec-dev/aztec-packages/build-images/src/home/.gitconfig -e FORCE_COLOR=true -e CPUS -e MEM aztecprotocol/build:3.0 /bin/bash -c 'timeout -v 600s bash -c '\''yarn-project/scripts/run_test.sh prover-node/src/prover-node.test.ts'\''' 16:07:31 + cid=d9fbe778fff5150efa175edb2b270e073b662c6caff858b2fd0366c38e4db06b 16:07:31 + set +x 16:07:38 [16:07:38.557] INFO: prover-node Stopping ProverNode 16:07:38 [16:07:38.588] WARN: prover-node Running promise was not started 16:07:38 [16:07:38.589] INFO: prover-node Stopped ProverNode 16:07:38 [16:07:38.746] INFO: prover-node Not starting proof for 10 since no blocks were found 16:07:38 [16:07:38.747] INFO: prover-node Stopping ProverNode 16:07:38 [16:07:38.748] WARN: prover-node Running promise was not started 16:07:38 [16:07:38.748] INFO: prover-node Stopped ProverNode 16:07:38 [16:07:38.951] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x252fd09e563a18252bb61140c7cdbc379ffb88c3ebf48c9944fa20533693fb83, 0x2f438c96d75382cd0af97a2439faae2ce06de38d39d7e136eeb4f38d2c593f8f, 0x1d95a9e1e8b682e37d33da82e2488a6635df2cfac7dda73dd88543a94c74d9eb 16:07:38 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 16:07:38 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 16:07:38 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 16:07:38 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 16:07:38 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 16:07:38 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 16:07:38 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 16:07:38 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 16:07:38 [16:07:38.952] INFO: prover-node Stopping ProverNode 16:07:38 [16:07:38.953] WARN: prover-node Running promise was not started 16:07:38 [16:07:38.954] INFO: prover-node Stopped ProverNode 16:07:39 [16:07:39.122] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 16:07:39 [16:07:39.122] INFO: prover-node Stopping ProverNode 16:07:39 [16:07:39.123] WARN: prover-node Running promise was not started 16:07:39 [16:07:39.123] INFO: prover-node Stopped ProverNode 16:07:39 [16:07:39.263] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 16:07:40 [16:07:40.267] INFO: prover-node Stopping ProverNode 16:07:40 [16:07:40.267] WARN: prover-node Running promise was not started 16:07:40 [16:07:40.267] INFO: prover-node Stopped ProverNode 16:07:40 [16:07:40.423] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 16:07:41 [16:07:41.424] INFO: prover-node Stopping ProverNode 16:07:41 [16:07:41.425] WARN: prover-node Running promise was not started 16:07:41 [16:07:41.425] INFO: prover-node Stopped ProverNode 16:07:41 PASS src/prover-node.test.ts (9.162 s) 16:07:41 prover-node 16:07:41 ✓ starts a proof on a finished epoch (523 ms) 16:07:41 ✓ does not start a proof if there are no blocks in the epoch (158 ms) 16:07:41 ✓ does not start a proof if there is a tx missing from coordinator (205 ms) 16:07:41 ✓ does not prove the same epoch twice (169 ms) 16:07:41 ✓ restarts a proof on a reorg (1144 ms) 16:07:41 ✓ does not restart a proof on an error (1157 ms) 16:07:41 16:07:41 Test Suites: 1 passed, 1 total 16:07:41 Tests: 6 passed, 6 total 16:07:41 Snapshots: 0 total 16:07:41 Time: 9.234 s 16:07:41 Ran all test suites matching prover-node/src/prover-node.test.ts. 16:07:41 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?