Parent Log:
http://ci.aztec-labs.com/b1869ed3b108a335
Command: 3f83527fe89c0976: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/b1b65bcdbd44a49fbebe5d2265256dc9466e92be
Env: REF_NAME=gh-readonly-queue/master/pr-15044-267ac35e8ccb487bdc79bbe12d428f4c8b4d4d9f CURRENT_VERSION=0.87.8 CI_FULL=0
Date: Fri Jun 13 16:28:22 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15044_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_a6b79aeaaf4803d9_master
16:28:22 +++ id -u
16:28:22 +++ id -g
16:28:22 ++ docker run -d --name prover-node_src_prover-node.test.ts --net=none --cpuset-cpus=0-63 --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:28:22 + cid=9937b0e281cbd70b33738301d507ea3b63f03bac354b35d48d166229087ce212
16:28:22 + set +x
16:28:27 [16:28:27.406]
INFO:
prover-node Stopping ProverNode
16:28:27 [16:28:27.410]
WARN:
prover-node Running promise was not started
16:28:27 [16:28:27.411]
INFO:
prover-node Stopped ProverNode
16:28:27 [16:28:27.529]
INFO:
prover-node Not starting proof for 10 since no blocks were found
16:28:27 [16:28:27.530]
INFO:
prover-node Stopping ProverNode
16:28:27 [16:28:27.530]
WARN:
prover-node Running promise was not started
16:28:27 [16:28:27.531]
INFO:
prover-node Stopped ProverNode
16:28:27 [16:28:27.654]
ERROR:
prover-node Error handling epoch completed: Error: Txs not found for epoch 10: 0x0c15da5235718bf5913541a7543f185be40b625d35e4e50911cb2d38fc4bbf63, 0x2973895c7c49992fccd525a0571a7bba67d33298d031da03582c04150fcc3feb, 0x04bc045b0d41d93fe09d0acb3a2e9e9a9bf0e384b98e281782a8d7b362f7ce7f
16:28:27 at TestProverNode.gatherTxs (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:358:11)
16:28:27 at TestProverNode.gatherEpochData (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:329:17)
16:28:27 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33
16:28:27 at TestProverNode.createProvingJob (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:280:23)
16:28:27 at /home/aztec-dev/aztec-packages/yarn-project/telemetry-client/dest/telemetry.js:34:33
16:28:27 at TestProverNode.startProof (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:197:17)
16:28:27 at TestProverNode.handleEpochReadyToProve (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.ts:139:7)
16:28:27 at Object.<anonymous> (/home/aztec-dev/aztec-packages/yarn-project/prover-node/src/prover-node.test.ts:173:5)
16:28:27 [16:28:27.655]
INFO:
prover-node Stopping ProverNode
16:28:27 [16:28:27.656]
WARN:
prover-node Running promise was not started
16:28:27 [16:28:27.657]
INFO:
prover-node Stopped ProverNode
16:28:27 [16:28:27.771]
WARN:
prover-node Not starting proof for 10 since there are active jobs for the epoch
{"activeJobs":["0"]}
16:28:27 [16:28:27.772]
INFO:
prover-node Stopping ProverNode
16:28:27 [16:28:27.772]
WARN:
prover-node Running promise was not started
16:28:27 [16:28:27.773]
INFO:
prover-node Stopped ProverNode
16:28:27 [16:28:27.888]
WARN:
prover-node Running new job for epoch 10 due to reorg
{"id":"0","epochNumber":10,"state":"reorg"}
16:28:28 [16:28:28.890]
INFO:
prover-node Stopping ProverNode
16:28:28 [16:28:28.890]
WARN:
prover-node Running promise was not started
16:28:28 [16:28:28.891]
INFO:
prover-node Stopped ProverNode
16:28:29 [16:28:29.000]
ERROR:
prover-node Job for 10 exited with state failed: { id: '0', epochNumber: 10n, state: 'failed' }
16:28:30 [16:28:30.001]
INFO:
prover-node Stopping ProverNode
16:28:30 [16:28:30.001]
WARN:
prover-node Running promise was not started
16:28:30 [16:28:30.002]
INFO:
prover-node Stopped ProverNode
16:28:30
PASS src/prover-node.test.ts (
6.532 s)
16:28:30 prover-node
16:28:30
✓ starts a proof on a finished epoch (200 ms)
16:28:30
✓ does not start a proof if there are no blocks in the epoch (119 ms)
16:28:30
✓ does not start a proof if there is a tx missing from coordinator (125 ms)
16:28:30
✓ does not prove the same epoch twice (116 ms)
16:28:30
✓ restarts a proof on a reorg (1118 ms)
16:28:30
✓ does not restart a proof on an error (1111 ms)
16:28:30
16:28:30
Test Suites: 1 passed, 1 total
16:28:30
Tests: 6 passed, 6 total
16:28:30
Snapshots: 0 total
16:28:30
Time: 6.593 s
16:28:30
Ran all test suites matching /prover-node\/src\/prover-node.test.ts/i
.
16:28:30
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?