Parent Log:
http://ci.aztec-labs.com/f612d45e6176d0af
Command: a1fcfb018e125472 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/308037ad9b1489540aedbb57a9dac3d71282010e
Env: REF_NAME=gh-readonly-queue/next/pr-15152-cb89edc02f7d386e48ee81660565d91895a3464b CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 12:40:03 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15152_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
12:40:07 [12:40:07.890]
INFO:
prover-client:proving-agent:job-controller-f40850ea Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.902]
INFO:
prover-client:proving-agent:job-controller-02fd7931 Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.931]
INFO:
prover-client:proving-agent:job-controller-c9abeb10 Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.932]
WARN:
prover-client:proving-agent:job-controller-c9abeb10 Aborted job controller for jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.932]
WARN:
prover-client:proving-agent:job-controller-c9abeb10 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
12:40:07 [12:40:07.936]
INFO:
prover-client:proving-agent:job-controller-90b97910 Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.940]
INFO:
prover-client:proving-agent:job-controller-8d28413b Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.946]
INFO:
prover-client:proving-agent:job-controller-bb79e426 Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.947]
WARN:
prover-client:proving-agent:job-controller-bb79e426 On complete handler error: Error: test error
{"jobId":"1"}
12:40:07 [12:40:07.952]
INFO:
prover-client:proving-agent:job-controller-970601fc Job controller started jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.954]
WARN:
prover-client:proving-agent:job-controller-970601fc Aborted job controller for jobId=1
{"jobId":"1"}
12:40:07 [12:40:07.961]
WARN:
prover-client:proving-agent:job-controller-970601fc Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
12:40:07
PASS src/proving_broker/proving_job_controller.test.ts
12:40:07 ProvingJobController
12:40:07
✓ reports IDLE status initially (7 ms)
12:40:07
✓ reports PROVING status while busy (14 ms)
12:40:07
✓ reports DONE status after job is done (30 ms)
12:40:07
✓ reports aborted error after cancellation (4 ms)
12:40:07
✓ calls onComplete (6 ms)
12:40:07
✓ calls onComplete with the error (2 ms)
12:40:07
✓ does not crash if onComplete throws (7 ms)
12:40:07
✓ calls onComplete if abort is called but result is masked (12 ms)
12:40:07
12:40:07
Test Suites: 1 passed, 1 total
12:40:07
Tests: 8 passed, 8 total
12:40:07
Snapshots: 0 total
12:40:07
Time: 3.599 s
12:40:07
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
12:40:07
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?