Parent Log: http://ci.aztec-labs.com/c148bc90788ce605 Command: 069d70048f6bf27e: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/08d3f55874836a573c4756b0cc7279160b0813a3 Env: REF_NAME=gh-readonly-queue/next/pr-15167-aac426c9418162aeee8162ed45014b9393d605b8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 10:05:42 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15167_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_next 10:05:42 +++ id -u 10:05:42 +++ id -g 10:05:42 ++ 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'\''' 10:05:42 + cid=e9c183d54fd628c597bf850b7e8deae5b34d33b82eb2d9287ef5fe042e44a976 10:05:42 + set +x 10:05:50 [10:05:50.158] INFO: prover-node Stopping ProverNode 10:05:50 [10:05:50.163] WARN: prover-node Running promise was not started 10:05:50 [10:05:50.164] INFO: prover-node Stopped ProverNode 10:05:50 [10:05:50.305] INFO: prover-node Not starting proof for 10 since no blocks were found 10:05:50 [10:05:50.306] INFO: prover-node Stopping ProverNode 10:05:50 [10:05:50.306] WARN: prover-node Running promise was not started 10:05:50 [10:05:50.307] INFO: prover-node Stopped ProverNode 10:05:50 [10:05:50.486] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x2060ea225ff7da5c30d03813f3f5a852802cb487e91b039ce5b5ec85b6208f09, 0x0f9944400144fb505a70265235c1944e11cddb38636a1262f8afa24599210cf1, 0x2372b1a6d4b30e5e3824eab667cef996f3b01a48f9b3bb096c27c6459c183c4e 10:05:50 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 10:05:50 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 10:05:50 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 10:05:50 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 10:05:50 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 10:05:50 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 10:05:50 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 10:05:50 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 10:05:50 [10:05:50.487] INFO: prover-node Stopping ProverNode 10:05:50 [10:05:50.488] WARN: prover-node Running promise was not started 10:05:50 [10:05:50.489] INFO: prover-node Stopped ProverNode 10:05:50 [10:05:50.644] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 10:05:50 [10:05:50.646] INFO: prover-node Stopping ProverNode 10:05:50 [10:05:50.646] WARN: prover-node Running promise was not started 10:05:50 [10:05:50.646] INFO: prover-node Stopped ProverNode 10:05:50 [10:05:50.824] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 10:05:51 [10:05:51.827] INFO: prover-node Stopping ProverNode 10:05:51 [10:05:51.827] WARN: prover-node Running promise was not started 10:05:51 [10:05:51.828] INFO: prover-node Stopped ProverNode 10:05:52 [10:05:52.067] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 10:05:53 [10:05:53.070] INFO: prover-node Stopping ProverNode 10:05:53 [10:05:53.072] WARN: prover-node Running promise was not started 10:05:53 [10:05:53.073] INFO: prover-node Stopped ProverNode 10:05:53 PASS src/prover-node.test.ts (9.147 s) 10:05:53 prover-node 10:05:53 ✓ starts a proof on a finished epoch (536 ms) 10:05:53 ✓ does not start a proof if there are no blocks in the epoch (141 ms) 10:05:53 ✓ does not start a proof if there is a tx missing from coordinator (182 ms) 10:05:53 ✓ does not prove the same epoch twice (157 ms) 10:05:53 ✓ restarts a proof on a reorg (1182 ms) 10:05:53 ✓ does not restart a proof on an error (1244 ms) 10:05:53 10:05:53 Test Suites: 1 passed, 1 total 10:05:53 Tests: 6 passed, 6 total 10:05:53 Snapshots: 0 total 10:05:53 Time: 9.254 s 10:05:53 Ran all test suites matching prover-node/src/prover-node.test.ts. 10:05:53 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?