Parent Log:
http://ci.aztec-labs.com/7fc79c48d0a2fc40
Command: 448a16f463e450de yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/80d800435dd8dfa325e38593d83b405488449dba
Env: REF_NAME=gh-readonly-queue/next/pr-14444-28bf32bfc2566751e8baa0a9125a9db20d474bee CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 15:58:42 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14444_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
15:58:46 [15:58:46.831]
INFO:
prover-client:proving-agent:job-controller-d7925845 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.841]
INFO:
prover-client:proving-agent:job-controller-800d37e2 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.865]
INFO:
prover-client:proving-agent:job-controller-4783c669 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.867]
WARN:
prover-client:proving-agent:job-controller-4783c669 Aborted job controller for jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.867]
WARN:
prover-client:proving-agent:job-controller-4783c669 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
15:58:46 [15:58:46.873]
INFO:
prover-client:proving-agent:job-controller-c5d829d9 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.878]
INFO:
prover-client:proving-agent:job-controller-92885d92 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.885]
INFO:
prover-client:proving-agent:job-controller-a036d1f5 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.885]
WARN:
prover-client:proving-agent:job-controller-a036d1f5 On complete handler error: Error: test error
{"jobId":"1"}
15:58:46 [15:58:46.888]
INFO:
prover-client:proving-agent:job-controller-949853f8 Job controller started jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.890]
WARN:
prover-client:proving-agent:job-controller-949853f8 Aborted job controller for jobId=1
{"jobId":"1"}
15:58:46 [15:58:46.895]
WARN:
prover-client:proving-agent:job-controller-949853f8 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
15:58:46
PASS src/proving_broker/proving_job_controller.test.ts
15:58:46 ProvingJobController
15:58:46
✓ reports IDLE status initially (6 ms)
15:58:46
✓ reports PROVING status while busy (13 ms)
15:58:46
✓ reports DONE status after job is done (23 ms)
15:58:46
✓ reports aborted error after cancellation (7 ms)
15:58:46
✓ calls onComplete (8 ms)
15:58:46
✓ calls onComplete with the error (4 ms)
15:58:46
✓ does not crash if onComplete throws (6 ms)
15:58:46
✓ calls onComplete if abort is called but result is masked (8 ms)
15:58:46
15:58:46
Test Suites: 1 passed, 1 total
15:58:46
Tests: 8 passed, 8 total
15:58:46
Snapshots: 0 total
15:58:46
Time: 3.381 s
15:58:46
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
15:58:46
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?