Parent Log: http://ci.aztec-labs.com/8ed5c55c2bfee19e Command: 9b90ba1cd25aa9c9: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/4ae29efe4b68ec58d68cf3708b9a36b94dad8b2b Env: REF_NAME=gh-readonly-queue/next/pr-15129-5c77169d7f01a9e15bc19b05fa231fd96111d7dd CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 15:18:49 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15129_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_next 15:18:49 +++ id -u 15:18:49 +++ id -g 15:18: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'\''' 15:18:49 + cid=f5c32e1f529ad39358b5b22da9e5ef5cd63e3ea258917304ca89b61d3813f8b6 15:18:49 + set +x 15:18:57 [15:18:57.216] INFO: prover-node Stopping ProverNode 15:18:57 [15:18:57.221] WARN: prover-node Running promise was not started 15:18:57 [15:18:57.222] INFO: prover-node Stopped ProverNode 15:18:57 [15:18:57.358] INFO: prover-node Not starting proof for 10 since no blocks were found 15:18:57 [15:18:57.359] INFO: prover-node Stopping ProverNode 15:18:57 [15:18:57.360] WARN: prover-node Running promise was not started 15:18:57 [15:18:57.360] INFO: prover-node Stopped ProverNode 15:18:57 [15:18:57.559] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x1ad2813f0f00deb38f3ca2fda107748f322473d29511f974de366826022ea9df, 0x29f834275589926e658f47dbfdc395a144d2a20363472831b6212f193bb75ed9, 0x2e99f397aeedc3fdacfa8849c951aa751ee5d3d22d07f19cef666e8a5049bb1a 15:18:57 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 15:18:57 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 15:18:57 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 15:18:57 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 15:18:57 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 15:18:57 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 15:18:57 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 15:18:57 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 15:18:57 [15:18:57.560] INFO: prover-node Stopping ProverNode 15:18:57 [15:18:57.561] WARN: prover-node Running promise was not started 15:18:57 [15:18:57.562] INFO: prover-node Stopped ProverNode 15:18:57 [15:18:57.769] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 15:18:57 [15:18:57.771] INFO: prover-node Stopping ProverNode 15:18:57 [15:18:57.771] WARN: prover-node Running promise was not started 15:18:57 [15:18:57.771] INFO: prover-node Stopped ProverNode 15:18:57 [15:18:57.950] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 15:18:58 [15:18:58.953] INFO: prover-node Stopping ProverNode 15:18:58 [15:18:58.953] WARN: prover-node Running promise was not started 15:18:58 [15:18:58.954] INFO: prover-node Stopped ProverNode 15:18:59 [15:18:59.116] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 15:19:00 [15:19:00.120] INFO: prover-node Stopping ProverNode 15:19:00 [15:19:00.131] WARN: prover-node Running promise was not started 15:19:00 [15:19:00.133] INFO: prover-node Stopped ProverNode 15:19:00 PASS src/prover-node.test.ts (9.445 s) 15:19:00 prover-node 15:19:00 ✓ starts a proof on a finished epoch (614 ms) 15:19:00 ✓ does not start a proof if there are no blocks in the epoch (138 ms) 15:19:00 ✓ does not start a proof if there is a tx missing from coordinator (202 ms) 15:19:00 ✓ does not prove the same epoch twice (209 ms) 15:19:00 ✓ restarts a proof on a reorg (1182 ms) 15:19:00 ✓ does not restart a proof on an error (1178 ms) 15:19:00 15:19:00 Test Suites: 1 passed, 1 total 15:19:00 Tests: 6 passed, 6 total 15:19:00 Snapshots: 0 total 15:19:00 Time: 9.552 s 15:19:00 Ran all test suites matching prover-node/src/prover-node.test.ts. 15:19:00 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?