Parent Log:
http://ci.aztec-labs.com/9ef2f13bc7b64e46
Command: 0742425f32083b75 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/04abcb151443d51d2f1b002a2412a083a9384a51
Env: REF_NAME=gh-readonly-queue/next/pr-15077-263498dd65e8700218979d7a94dbfd25b2a8a8a8 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 20:52:11 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15077_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
20:52:15 [20:52:15.248]
INFO:
prover-client:proving-agent:job-controller-a6952d19 Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.259]
INFO:
prover-client:proving-agent:job-controller-78d099be Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.278]
INFO:
prover-client:proving-agent:job-controller-2d3e283c Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.279]
WARN:
prover-client:proving-agent:job-controller-2d3e283c Aborted job controller for jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.280]
WARN:
prover-client:proving-agent:job-controller-2d3e283c Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:52:15 [20:52:15.286]
INFO:
prover-client:proving-agent:job-controller-5d71a845 Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.292]
INFO:
prover-client:proving-agent:job-controller-8981bc30 Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.300]
INFO:
prover-client:proving-agent:job-controller-850b8ec1 Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.301]
WARN:
prover-client:proving-agent:job-controller-850b8ec1 On complete handler error: Error: test error
{"jobId":"1"}
20:52:15 [20:52:15.305]
INFO:
prover-client:proving-agent:job-controller-08a22f0b Job controller started jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.307]
WARN:
prover-client:proving-agent:job-controller-08a22f0b Aborted job controller for jobId=1
{"jobId":"1"}
20:52:15 [20:52:15.313]
WARN:
prover-client:proving-agent:job-controller-08a22f0b Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:52:15
PASS src/proving_broker/proving_job_controller.test.ts
20:52:15 ProvingJobController
20:52:15
✓ reports IDLE status initially (6 ms)
20:52:15
✓ reports PROVING status while busy (12 ms)
20:52:15
✓ reports DONE status after job is done (19 ms)
20:52:15
✓ reports aborted error after cancellation (8 ms)
20:52:15
✓ calls onComplete (8 ms)
20:52:15
✓ calls onComplete with the error (5 ms)
20:52:15
✓ does not crash if onComplete throws (7 ms)
20:52:15
✓ calls onComplete if abort is called but result is masked (11 ms)
20:52:15
20:52:15
Test Suites: 1 passed, 1 total
20:52:15
Tests: 8 passed, 8 total
20:52:15
Snapshots: 0 total
20:52:15
Time: 3.061 s
20:52:15
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
20:52:15
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?