Parent Log: http://ci.aztec-labs.com/6348f16c9c1344f2 Command: ca4daf70a894f3c3: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/f0619dd82429a5973f3e1da8d7eb0877264908e3 Env: REF_NAME=gh-readonly-queue/next/pr-15188-ef6780e77e5f82f98ddfe92fd387cfd5fa7682e8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 16:10:49 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15188_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_next 16:10:49 +++ id -u 16:10:49 +++ id -g 16:10:49 ++ 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:10:49 + cid=bf19622ef0fa4b1600757bc2e9708dff975b6df911fc1ea6bb37dfae3ec35537 16:10:49 + set +x 16:10:57 [16:10:57.211] INFO: prover-node Stopping ProverNode 16:10:57 [16:10:57.217] WARN: prover-node Running promise was not started 16:10:57 [16:10:57.218] INFO: prover-node Stopped ProverNode 16:10:57 [16:10:57.396] INFO: prover-node Not starting proof for 10 since no blocks were found 16:10:57 [16:10:57.397] INFO: prover-node Stopping ProverNode 16:10:57 [16:10:57.397] WARN: prover-node Running promise was not started 16:10:57 [16:10:57.398] INFO: prover-node Stopped ProverNode 16:10:57 [16:10:57.567] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x153980c296e1a04c6de9c47f624884601dd14f5182d082c794e7e1b3a3ce69e6, 0x0d55eb4d4589fac86e390263b47d01139e513f257e76f16c954e16a80443a17f, 0x0e0bdc7117a799ebb9b457ecb316a810e1f01bd037b69a2d2064f7c170ca636e 16:10:57 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 16:10:57 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 16:10:57 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 16:10:57 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 16:10:57 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 16:10:57 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 16:10:57 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 16:10:57 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 16:10:57 [16:10:57.568] INFO: prover-node Stopping ProverNode 16:10:57 [16:10:57.569] WARN: prover-node Running promise was not started 16:10:57 [16:10:57.570] INFO: prover-node Stopped ProverNode 16:10:57 [16:10:57.711] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 16:10:57 [16:10:57.712] INFO: prover-node Stopping ProverNode 16:10:57 [16:10:57.712] WARN: prover-node Running promise was not started 16:10:57 [16:10:57.713] INFO: prover-node Stopped ProverNode 16:10:57 [16:10:57.863] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 16:10:58 [16:10:58.865] INFO: prover-node Stopping ProverNode 16:10:58 [16:10:58.867] WARN: prover-node Running promise was not started 16:10:58 [16:10:58.868] INFO: prover-node Stopped ProverNode 16:10:59 [16:10:59.042] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 16:11:00 [16:11:00.044] INFO: prover-node Stopping ProverNode 16:11:00 [16:11:00.044] WARN: prover-node Running promise was not started 16:11:00 [16:11:00.046] INFO: prover-node Stopped ProverNode 16:11:00 PASS src/prover-node.test.ts (9.215 s) 16:11:00 prover-node 16:11:00 ✓ starts a proof on a finished epoch (622 ms) 16:11:00 ✓ does not start a proof if there are no blocks in the epoch (178 ms) 16:11:00 ✓ does not start a proof if there is a tx missing from coordinator (171 ms) 16:11:00 ✓ does not prove the same epoch twice (142 ms) 16:11:00 ✓ restarts a proof on a reorg (1156 ms) 16:11:00 ✓ does not restart a proof on an error (1178 ms) 16:11:00 16:11:00 Test Suites: 1 passed, 1 total 16:11:00 Tests: 6 passed, 6 total 16:11:00 Snapshots: 0 total 16:11:00 Time: 9.303 s 16:11:00 Ran all test suites matching prover-node/src/prover-node.test.ts. 16:11:00 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?