Parent Log: http://ci.aztec-labs.com/4a6d30c36bb1e847 Command: d57d38082bbaf86d: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/fdc8ff50dee1a2a8a98393ff5069a285b52efa1f Env: REF_NAME=gh-readonly-queue/next/pr-15187-9b8ea5acda76687342ddb62595e293281661f029 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 23 09:39: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 09:39:30 +++ id -u 09:39:30 +++ id -g 09:39: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'\''' 09:39:31 + cid=f3656be26657529996944f58f6a4df74a90c8a44fb16952b52b4966b75b42d84 09:39:31 + set +x 09:39:38 [09:39:38.818] INFO: prover-node Stopping ProverNode 09:39:38 [09:39:38.824] WARN: prover-node Running promise was not started 09:39:38 [09:39:38.825] INFO: prover-node Stopped ProverNode 09:39:39 [09:39:39.010] INFO: prover-node Not starting proof for 10 since no blocks were found 09:39:39 [09:39:39.011] INFO: prover-node Stopping ProverNode 09:39:39 [09:39:39.012] WARN: prover-node Running promise was not started 09:39:39 [09:39:39.012] INFO: prover-node Stopped ProverNode 09:39:39 [09:39:39.210] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x163361c3c667719f76058f7964479e821bee19dbf804313d38bd8fc3e637760f, 0x277f57721f8b64bc84dcf756ea45435e85f384974faf7cb1453d5ca62e432fe3, 0x0c913ed9059683a4d890304e675f51a0ac8c70c9e0344b5fb687c3f1e00aba78 09:39:39 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 09:39:39 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 09:39:39 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 09:39:39 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 09:39:39 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 09:39:39 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 09:39:39 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 09:39:39 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 09:39:39 [09:39:39.211] INFO: prover-node Stopping ProverNode 09:39:39 [09:39:39.212] WARN: prover-node Running promise was not started 09:39:39 [09:39:39.213] INFO: prover-node Stopped ProverNode 09:39:39 [09:39:39.362] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 09:39:39 [09:39:39.363] INFO: prover-node Stopping ProverNode 09:39:39 [09:39:39.364] WARN: prover-node Running promise was not started 09:39:39 [09:39:39.364] INFO: prover-node Stopped ProverNode 09:39:39 [09:39:39.538] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 09:39:40 [09:39:40.540] INFO: prover-node Stopping ProverNode 09:39:40 [09:39:40.540] WARN: prover-node Running promise was not started 09:39:40 [09:39:40.541] INFO: prover-node Stopped ProverNode 09:39:40 [09:39:40.714] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 09:39:41 [09:39:41.716] INFO: prover-node Stopping ProverNode 09:39:41 [09:39:41.717] WARN: prover-node Running promise was not started 09:39:41 [09:39:41.718] INFO: prover-node Stopped ProverNode 09:39:41 PASS src/prover-node.test.ts (9.628 s) 09:39:41 prover-node 09:39:41 ✓ starts a proof on a finished epoch (621 ms) 09:39:41 ✓ does not start a proof if there are no blocks in the epoch (186 ms) 09:39:41 ✓ does not start a proof if there is a tx missing from coordinator (200 ms) 09:39:41 ✓ does not prove the same epoch twice (150 ms) 09:39:41 ✓ restarts a proof on a reorg (1176 ms) 09:39:41 ✓ does not restart a proof on an error (1177 ms) 09:39:41 09:39:41 Test Suites: 1 passed, 1 total 09:39:41 Tests: 6 passed, 6 total 09:39:41 Snapshots: 0 total 09:39:41 Time: 9.708 s 09:39:41 Ran all test suites matching prover-node/src/prover-node.test.ts. 09:39:41 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?