Parent Log:
http://ci.aztec-labs.com/32bd56bf1f1fe84d
Command: 3f1d1d87da1584d1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/aac426c9418162aeee8162ed45014b9393d605b8
Env: REF_NAME=gh-readonly-queue/next/pr-15051-92d685c3a802eb31897b6f13d28b9ee428c73744 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 06:36:25 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15051_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
06:36:29 [06:36:29.505]
INFO:
prover-client:proving-agent:job-controller-4e6315a9 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.513]
INFO:
prover-client:proving-agent:job-controller-4b7adca0 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.555]
INFO:
prover-client:proving-agent:job-controller-d7e5dbb3 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.555]
WARN:
prover-client:proving-agent:job-controller-d7e5dbb3 Aborted job controller for jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.556]
WARN:
prover-client:proving-agent:job-controller-d7e5dbb3 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
06:36:29 [06:36:29.559]
INFO:
prover-client:proving-agent:job-controller-2798615f Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.563]
INFO:
prover-client:proving-agent:job-controller-3cf00938 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.568]
INFO:
prover-client:proving-agent:job-controller-c64645c4 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.568]
WARN:
prover-client:proving-agent:job-controller-c64645c4 On complete handler error: Error: test error
{"jobId":"1"}
06:36:29 [06:36:29.570]
INFO:
prover-client:proving-agent:job-controller-fa9c1042 Job controller started jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.572]
WARN:
prover-client:proving-agent:job-controller-fa9c1042 Aborted job controller for jobId=1
{"jobId":"1"}
06:36:29 [06:36:29.577]
WARN:
prover-client:proving-agent:job-controller-fa9c1042 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
06:36:29
PASS src/proving_broker/proving_job_controller.test.ts
06:36:29 ProvingJobController
06:36:29
✓ reports IDLE status initially (4 ms)
06:36:29
✓ reports PROVING status while busy (10 ms)
06:36:29
✓ reports DONE status after job is done (41 ms)
06:36:29
✓ reports aborted error after cancellation (5 ms)
06:36:29
✓ calls onComplete (5 ms)
06:36:29
✓ calls onComplete with the error (2 ms)
06:36:29
✓ does not crash if onComplete throws (4 ms)
06:36:29
✓ calls onComplete if abort is called but result is masked (8 ms)
06:36:29
06:36:29
Test Suites: 1 passed, 1 total
06:36:29
Tests: 8 passed, 8 total
06:36:29
Snapshots: 0 total
06:36:29
Time: 2.935 s
06:36:29
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
06:36:29
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?