Parent Log:
http://ci.aztec-labs.com/9ede61bfdff30c23
Command: 03ab2c8f0cfe2a95 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/77a00686be4080a71b03d68671da6c8b270b62aa
Env: REF_NAME=gh-readonly-queue/next/pr-14961-fa23733be8278348dff0959c8094bcfd89eb44d5 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Thu Jun 12 10:50:08 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14961_amd64_x4-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:50:11 [10:50:11.434]
INFO:
prover-client:proving-agent:job-controller-1d771bd2 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.445]
INFO:
prover-client:proving-agent:job-controller-e3af5954 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.456]
INFO:
prover-client:proving-agent:job-controller-4f0e9d64 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.457]
WARN:
prover-client:proving-agent:job-controller-4f0e9d64 Aborted job controller for jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.458]
WARN:
prover-client:proving-agent:job-controller-4f0e9d64 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:50:11 [10:50:11.463]
INFO:
prover-client:proving-agent:job-controller-7e121f5f Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.467]
INFO:
prover-client:proving-agent:job-controller-7fec58a4 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.472]
INFO:
prover-client:proving-agent:job-controller-8565ce61 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.473]
WARN:
prover-client:proving-agent:job-controller-8565ce61 On complete handler error: Error: test error
{"jobId":"1"}
10:50:11 [10:50:11.476]
INFO:
prover-client:proving-agent:job-controller-317fe058 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.478]
WARN:
prover-client:proving-agent:job-controller-317fe058 Aborted job controller for jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.482]
WARN:
prover-client:proving-agent:job-controller-317fe058 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:50:11
PASS src/proving_broker/proving_job_controller.test.ts
10:50:11 ProvingJobController
10:50:11
✓ reports IDLE status initially (4 ms)
10:50:11
✓ reports PROVING status while busy (12 ms)
10:50:11
✓ reports DONE status after job is done (11 ms)
10:50:11
✓ reports aborted error after cancellation (6 ms)
10:50:11
✓ calls onComplete (6 ms)
10:50:11
✓ calls onComplete with the error (3 ms)
10:50:11
✓ does not crash if onComplete throws (5 ms)
10:50:11
✓ calls onComplete if abort is called but result is masked (9 ms)
10:50:11
10:50:11
Test Suites: 1 passed, 1 total
10:50:11
Tests: 8 passed, 8 total
10:50:11
Snapshots: 0 total
10:50:11
Time: 2.502 s
10:50:11
Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i
.
10:50:11
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?