Parent Log:
http://ci.aztec-labs.com/34a1c30ebc4985df
Command: a8cc061dbe484831 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/c2e27576e66fad0caaa136e905b8439d70c05e37
Env: REF_NAME=gh-readonly-queue/next/pr-15181-58696523cc93fda453138a4f2c2dff72b21f0bfa CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 13:20:05 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15181_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
13:20:09 [13:20:09.645]
INFO:
prover-client:proving-agent:job-controller-683d910a Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.654]
INFO:
prover-client:proving-agent:job-controller-5ddc1416 Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.667]
INFO:
prover-client:proving-agent:job-controller-dbc23d7f Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.668]
WARN:
prover-client:proving-agent:job-controller-dbc23d7f Aborted job controller for jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.668]
WARN:
prover-client:proving-agent:job-controller-dbc23d7f Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:20:09 [13:20:09.673]
INFO:
prover-client:proving-agent:job-controller-bf52e984 Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.676]
INFO:
prover-client:proving-agent:job-controller-0b448e08 Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.680]
INFO:
prover-client:proving-agent:job-controller-c13320c6 Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.681]
WARN:
prover-client:proving-agent:job-controller-c13320c6 On complete handler error: Error: test error
{"jobId":"1"}
13:20:09 [13:20:09.683]
INFO:
prover-client:proving-agent:job-controller-4edd7a0e Job controller started jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.688]
WARN:
prover-client:proving-agent:job-controller-4edd7a0e Aborted job controller for jobId=1
{"jobId":"1"}
13:20:09 [13:20:09.693]
WARN:
prover-client:proving-agent:job-controller-4edd7a0e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:20:09
PASS src/proving_broker/proving_job_controller.test.ts
13:20:09 ProvingJobController
13:20:09
✓ reports IDLE status initially (4 ms)
13:20:09
✓ reports PROVING status while busy (11 ms)
13:20:09
✓ reports DONE status after job is done (13 ms)
13:20:09
✓ reports aborted error after cancellation (5 ms)
13:20:09
✓ calls onComplete (5 ms)
13:20:09
✓ calls onComplete with the error (3 ms)
13:20:09
✓ does not crash if onComplete throws (4 ms)
13:20:09
✓ calls onComplete if abort is called but result is masked (12 ms)
13:20:09
13:20:09
Test Suites: 1 passed, 1 total
13:20:09
Tests: 8 passed, 8 total
13:20:09
Snapshots: 0 total
13:20:09
Time: 3.599 s
13:20:09
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
13:20:09
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?