Parent Log:
http://ci.aztec-labs.com/ef28baa8c095c429
Command: 13dd8684e4e32fd7 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/1c9ca312bfdace816082212846900a49694e1e50
Env: REF_NAME=gh-readonly-queue/next/pr-15182-af094bce13530e078c78de9f3264280e6693d533 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 24 08:55:45 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15182_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
08:55:50 [08:55:50.126]
INFO:
prover-client:proving-agent:job-controller-1df1ca15 Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.138]
INFO:
prover-client:proving-agent:job-controller-6504da32 Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.152]
INFO:
prover-client:proving-agent:job-controller-79f54ff8 Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.154]
WARN:
prover-client:proving-agent:job-controller-79f54ff8 Aborted job controller for jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.154]
WARN:
prover-client:proving-agent:job-controller-79f54ff8 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
08:55:50 [08:55:50.160]
INFO:
prover-client:proving-agent:job-controller-0adf2dc4 Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.165]
INFO:
prover-client:proving-agent:job-controller-79b5130a Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.171]
INFO:
prover-client:proving-agent:job-controller-2432a81d Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.171]
WARN:
prover-client:proving-agent:job-controller-2432a81d On complete handler error: Error: test error
{"jobId":"1"}
08:55:50 [08:55:50.174]
INFO:
prover-client:proving-agent:job-controller-68f25322 Job controller started jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.176]
WARN:
prover-client:proving-agent:job-controller-68f25322 Aborted job controller for jobId=1
{"jobId":"1"}
08:55:50 [08:55:50.180]
WARN:
prover-client:proving-agent:job-controller-68f25322 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
08:55:50
PASS src/proving_broker/proving_job_controller.test.ts
08:55:50 ProvingJobController
08:55:50
✓ reports IDLE status initially (5 ms)
08:55:50
✓ reports PROVING status while busy (15 ms)
08:55:50
✓ reports DONE status after job is done (14 ms)
08:55:50
✓ reports aborted error after cancellation (7 ms)
08:55:50
✓ calls onComplete (7 ms)
08:55:50
✓ calls onComplete with the error (3 ms)
08:55:50
✓ does not crash if onComplete throws (5 ms)
08:55:50
✓ calls onComplete if abort is called but result is masked (9 ms)
08:55:50
08:55:50
Test Suites: 1 passed, 1 total
08:55:50
Tests: 8 passed, 8 total
08:55:50
Snapshots: 0 total
08:55:50
Time: 3.782 s
08:55:50
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
08:55:50
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?