Parent Log:
http://ci.aztec-labs.com/5b0c3de501d8603e
Command: 4ef547fa5e299294 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/016def8adbfe93f34b41a41f439b146b5318c895
Env: REF_NAME=gh-readonly-queue/next/pr-15237-d4893155ff105399557b55c16450c39921c70d11 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 24 11:55:50 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15237_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
11:55:55 [11:55:55.278]
INFO:
prover-client:proving-agent:job-controller-81eadda8 Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.286]
INFO:
prover-client:proving-agent:job-controller-bd52fa37 Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.307]
INFO:
prover-client:proving-agent:job-controller-92dd21b5 Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.308]
WARN:
prover-client:proving-agent:job-controller-92dd21b5 Aborted job controller for jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.309]
WARN:
prover-client:proving-agent:job-controller-92dd21b5 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:55:55 [11:55:55.313]
INFO:
prover-client:proving-agent:job-controller-207dd16c Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.319]
INFO:
prover-client:proving-agent:job-controller-fba97cfb Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.325]
INFO:
prover-client:proving-agent:job-controller-a09b14b6 Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.326]
WARN:
prover-client:proving-agent:job-controller-a09b14b6 On complete handler error: Error: test error
{"jobId":"1"}
11:55:55 [11:55:55.328]
INFO:
prover-client:proving-agent:job-controller-beda09c5 Job controller started jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.330]
WARN:
prover-client:proving-agent:job-controller-beda09c5 Aborted job controller for jobId=1
{"jobId":"1"}
11:55:55 [11:55:55.334]
WARN:
prover-client:proving-agent:job-controller-beda09c5 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:55:55
PASS src/proving_broker/proving_job_controller.test.ts
11:55:55 ProvingJobController
11:55:55
✓ reports IDLE status initially (5 ms)
11:55:55
✓ reports PROVING status while busy (10 ms)
11:55:55
✓ reports DONE status after job is done (20 ms)
11:55:55
✓ reports aborted error after cancellation (6 ms)
11:55:55
✓ calls onComplete (6 ms)
11:55:55
✓ calls onComplete with the error (4 ms)
11:55:55
✓ does not crash if onComplete throws (6 ms)
11:55:55
✓ calls onComplete if abort is called but result is masked (8 ms)
11:55:55
11:55:55
Test Suites: 1 passed, 1 total
11:55:55
Tests: 8 passed, 8 total
11:55:55
Snapshots: 0 total
11:55:55
Time: 4.025 s
11:55:55
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
11:55:55
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?