Parent Log:
http://ci.aztec-labs.com/2d9e34481bb091c3
Command: 1f25be2e8c7902e7 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/17ea18ade041a1bb437806e047c30b29da124094
Env: REF_NAME=gh-readonly-queue/next/pr-15007-4c695be4bff40a4a2ca2118c7e14c83a104e93aa CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 17:26:10 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15007_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
17:26:15 [17:26:15.140]
INFO:
prover-client:proving-agent:job-controller-68083d2e Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.151]
INFO:
prover-client:proving-agent:job-controller-1e5558b0 Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.164]
INFO:
prover-client:proving-agent:job-controller-4e01b79a Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.165]
WARN:
prover-client:proving-agent:job-controller-4e01b79a Aborted job controller for jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.165]
WARN:
prover-client:proving-agent:job-controller-4e01b79a Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:26:15 [17:26:15.172]
INFO:
prover-client:proving-agent:job-controller-9647bdf5 Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.179]
INFO:
prover-client:proving-agent:job-controller-f4556fcc Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.184]
INFO:
prover-client:proving-agent:job-controller-57d058d6 Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.185]
WARN:
prover-client:proving-agent:job-controller-57d058d6 On complete handler error: Error: test error
{"jobId":"1"}
17:26:15 [17:26:15.187]
INFO:
prover-client:proving-agent:job-controller-ec87cfd9 Job controller started jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.188]
WARN:
prover-client:proving-agent:job-controller-ec87cfd9 Aborted job controller for jobId=1
{"jobId":"1"}
17:26:15 [17:26:15.192]
WARN:
prover-client:proving-agent:job-controller-ec87cfd9 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:26:15
PASS src/proving_broker/proving_job_controller.test.ts
17:26:15 ProvingJobController
17:26:15
✓ reports IDLE status initially (6 ms)
17:26:15
✓ reports PROVING status while busy (12 ms)
17:26:15
✓ reports DONE status after job is done (12 ms)
17:26:15
✓ reports aborted error after cancellation (7 ms)
17:26:15
✓ calls onComplete (8 ms)
17:26:15
✓ calls onComplete with the error (3 ms)
17:26:15
✓ does not crash if onComplete throws (5 ms)
17:26:15
✓ calls onComplete if abort is called but result is masked (7 ms)
17:26:15
17:26:15
Test Suites: 1 passed, 1 total
17:26:15
Tests: 8 passed, 8 total
17:26:15
Snapshots: 0 total
17:26:15
Time: 3.952 s
17:26:15
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
17:26:15
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?