Parent Log: http://ci.aztec-labs.com/bf9a1f2309b2f82d Command: f44e1b4f382283e1: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/7d1abcb337009939ee47da8445b5fee80f39fb58 Env: REF_NAME=gh-readonly-queue/next/pr-15156-df137f9440a970af2eb6e2ee94c48bf3bf47e207 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 10:05:24 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15156_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_next 10:05:24 +++ id -u 10:05:24 +++ id -g 10:05:24 ++ 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:24 + cid=f72c7a87c8f03f0f89bea8afa787b91a596ee2119a119251ef0a9e5cee39d6a7 10:05:24 + set +x 10:05:32 [10:05:32.239] INFO: prover-node Stopping ProverNode 10:05:32 [10:05:32.245] WARN: prover-node Running promise was not started 10:05:32 [10:05:32.246] INFO: prover-node Stopped ProverNode 10:05:32 [10:05:32.438] INFO: prover-node Not starting proof for 10 since no blocks were found 10:05:32 [10:05:32.439] INFO: prover-node Stopping ProverNode 10:05:32 [10:05:32.440] WARN: prover-node Running promise was not started 10:05:32 [10:05:32.440] INFO: prover-node Stopped ProverNode 10:05:32 [10:05:32.743] ERROR: prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x007e3e76c887b990547a9005d5271a7c2c6aa6e1d9846f78910075ce64374a93, 0x131a6488e96aa9e8e2e8a76d7bfa8f8d8e1c29875237afa6c8d6b139de563482, 0x1d85c45215126b9f5e698fbed4c814d9d03114ec1ccb6d3a749c415a08583384 10:05:32 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11) 10:05:32 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17) 10:05:32 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 10:05:32 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23) 10:05:32 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33 10:05:32 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17) 10:05:32 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7) 10:05:32 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5) 10:05:32 [10:05:32.744] INFO: prover-node Stopping ProverNode 10:05:32 [10:05:32.745] WARN: prover-node Running promise was not started 10:05:32 [10:05:32.746] INFO: prover-node Stopped ProverNode 10:05:33 [10:05:33.000] WARN: prover-node Not starting proof for 10 since there are active jobs for the epoch {"activeJobs":["0"]} 10:05:33 [10:05:33.002] INFO: prover-node Stopping ProverNode 10:05:33 [10:05:33.002] WARN: prover-node Running promise was not started 10:05:33 [10:05:33.002] INFO: prover-node Stopped ProverNode 10:05:33 [10:05:33.220] WARN: prover-node Running new job for epoch 10 due to reorg {"id":"0","epochNumber":10,"state":"reorg"} 10:05:34 [10:05:34.224] INFO: prover-node Stopping ProverNode 10:05:34 [10:05:34.225] WARN: prover-node Running promise was not started 10:05:34 [10:05:34.225] INFO: prover-node Stopped ProverNode 10:05:34 [10:05:34.376] ERROR: prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' } 10:05:35 [10:05:35.378] INFO: prover-node Stopping ProverNode 10:05:35 [10:05:35.379] WARN: prover-node Running promise was not started 10:05:35 [10:05:35.380] INFO: prover-node Stopped ProverNode 10:05:35 PASS src/prover-node.test.ts (9.809 s) 10:05:35 prover-node 10:05:35 ✓ starts a proof on a finished epoch (529 ms) 10:05:35 ✓ does not start a proof if there are no blocks in the epoch (194 ms) 10:05:35 ✓ does not start a proof if there is a tx missing from coordinator (305 ms) 10:05:35 ✓ does not prove the same epoch twice (256 ms) 10:05:35 ✓ restarts a proof on a reorg (1223 ms) 10:05:35 ✓ does not restart a proof on an error (1155 ms) 10:05:35 10:05:35 Test Suites: 1 passed, 1 total 10:05:35 Tests: 6 passed, 6 total 10:05:35 Snapshots: 0 total 10:05:35 Time: 9.92 s 10:05:35 Ran all test suites matching prover-node/src/prover-node.test.ts. 10:05:35 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?