Parent Log:
http://ci.aztec-labs.com/b032927225b2903d
Command: 5f41952f8889ac40 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/1650b3d017a2a4fa5182c8787e79cc108e24e1f4
Env: REF_NAME=gh-readonly-queue/next/pr-14990-77a00686be4080a71b03d68671da6c8b270b62aa CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Thu Jun 12 10:50:07 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14990_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:50:10 [10:50:10.964]
INFO:
prover-client:proving-agent:job-controller-ac9dfab7 Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.973]
INFO:
prover-client:proving-agent:job-controller-1f34aba0 Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.985]
INFO:
prover-client:proving-agent:job-controller-b49474a1 Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.986]
WARN:
prover-client:proving-agent:job-controller-b49474a1 Aborted job controller for jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.986]
WARN:
prover-client:proving-agent:job-controller-b49474a1 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:50:10 [10:50:10.989]
INFO:
prover-client:proving-agent:job-controller-2195f181 Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.994]
INFO:
prover-client:proving-agent:job-controller-39982eac Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.998]
INFO:
prover-client:proving-agent:job-controller-3f7f6bcb Job controller started jobId=1
{"jobId":"1"}
10:50:10 [10:50:10.999]
WARN:
prover-client:proving-agent:job-controller-3f7f6bcb On complete handler error: Error: test error
{"jobId":"1"}
10:50:10 [10:50:11.000]
INFO:
prover-client:proving-agent:job-controller-1f4671f3 Job controller started jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.002]
WARN:
prover-client:proving-agent:job-controller-1f4671f3 Aborted job controller for jobId=1
{"jobId":"1"}
10:50:11 [10:50:11.007]
WARN:
prover-client:proving-agent:job-controller-1f4671f3 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 (6 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 (4 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 (4 ms)
10:50:11
✓ calls onComplete if abort is called but result is masked (8 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.466 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?