Parent Log:
http://ci.aztec-labs.com/a9198a30c600dd3e
Command: 48483af633053ffe yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/3b44f825dcd3249b2c8a1105905fa3394aa7213d
Env: REF_NAME=gh-readonly-queue/next/pr-15041-eeab628a4e44477cb6796c5a461ee0c0bb332d75 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 17:46:59 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15041_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
17:47:03 [17:47:03.995]
INFO:
prover-client:proving-agent:job-controller-176a8422 Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.005]
INFO:
prover-client:proving-agent:job-controller-1804e0ff Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.022]
INFO:
prover-client:proving-agent:job-controller-6af15514 Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.023]
WARN:
prover-client:proving-agent:job-controller-6af15514 Aborted job controller for jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.024]
WARN:
prover-client:proving-agent:job-controller-6af15514 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:47:04 [17:47:04.030]
INFO:
prover-client:proving-agent:job-controller-759cd4e9 Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.035]
INFO:
prover-client:proving-agent:job-controller-282dc584 Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.040]
INFO:
prover-client:proving-agent:job-controller-a8231701 Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.041]
WARN:
prover-client:proving-agent:job-controller-a8231701 On complete handler error: Error: test error
{"jobId":"1"}
17:47:04 [17:47:04.043]
INFO:
prover-client:proving-agent:job-controller-28c6b63d Job controller started jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.046]
WARN:
prover-client:proving-agent:job-controller-28c6b63d Aborted job controller for jobId=1
{"jobId":"1"}
17:47:04 [17:47:04.051]
WARN:
prover-client:proving-agent:job-controller-28c6b63d Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:47:04
PASS src/proving_broker/proving_job_controller.test.ts
17:47:04 ProvingJobController
17:47:04
✓ reports IDLE status initially (5 ms)
17:47:04
✓ reports PROVING status while busy (11 ms)
17:47:04
✓ reports DONE status after job is done (16 ms)
17:47:04
✓ reports aborted error after cancellation (8 ms)
17:47:04
✓ calls onComplete (7 ms)
17:47:04
✓ calls onComplete with the error (3 ms)
17:47:04
✓ does not crash if onComplete throws (5 ms)
17:47:04
✓ calls onComplete if abort is called but result is masked (11 ms)
17:47:04
17:47:04
Test Suites: 1 passed, 1 total
17:47:04
Tests: 8 passed, 8 total
17:47:04
Snapshots: 0 total
17:47:04
Time: 3.735 s
17:47:04
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
17:47:04
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?