Parent Log:
http://ci.aztec-labs.com/6379f596748997ca
Command: 2ca1986c0c6d5c2c yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/9222c7777effe26aa04b5367a455d25be0e7f62e
Env: REF_NAME=gh-readonly-queue/next/pr-15055-a9bb2f683797c8e631b892c5f539a2867bddaabf CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 16:02:47 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15055_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
16:02:52 [16:02:52.795]
INFO:
prover-client:proving-agent:job-controller-da40b681 Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.802]
INFO:
prover-client:proving-agent:job-controller-68cee6bc Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.819]
INFO:
prover-client:proving-agent:job-controller-dfcce2c5 Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.821]
WARN:
prover-client:proving-agent:job-controller-dfcce2c5 Aborted job controller for jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.822]
WARN:
prover-client:proving-agent:job-controller-dfcce2c5 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:02:52 [16:02:52.841]
INFO:
prover-client:proving-agent:job-controller-b978a821 Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.845]
INFO:
prover-client:proving-agent:job-controller-1ac9d282 Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.851]
INFO:
prover-client:proving-agent:job-controller-2f0f89fb Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.852]
WARN:
prover-client:proving-agent:job-controller-2f0f89fb On complete handler error: Error: test error
{"jobId":"1"}
16:02:52 [16:02:52.855]
INFO:
prover-client:proving-agent:job-controller-6c328e9d Job controller started jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.857]
WARN:
prover-client:proving-agent:job-controller-6c328e9d Aborted job controller for jobId=1
{"jobId":"1"}
16:02:52 [16:02:52.862]
WARN:
prover-client:proving-agent:job-controller-6c328e9d Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:02:52
PASS src/proving_broker/proving_job_controller.test.ts
16:02:52 ProvingJobController
16:02:52
✓ reports IDLE status initially (4 ms)
16:02:52
✓ reports PROVING status while busy (9 ms)
16:02:52
✓ reports DONE status after job is done (16 ms)
16:02:52
✓ reports aborted error after cancellation (21 ms)
16:02:52
✓ calls onComplete (7 ms)
16:02:52
✓ calls onComplete with the error (4 ms)
16:02:52
✓ does not crash if onComplete throws (5 ms)
16:02:52
✓ calls onComplete if abort is called but result is masked (9 ms)
16:02:52
16:02:52
Test Suites: 1 passed, 1 total
16:02:52
Tests: 8 passed, 8 total
16:02:52
Snapshots: 0 total
16:02:52
Time: 4.079 s
16:02:52
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
16:02:52
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?