Parent Log:
http://ci.aztec-labs.com/a82668a8e8b2c62c
Command: 3713b4397d55fa0c yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/314d7622c6bacc8333ae49fe9583967cab78349b
Env: REF_NAME=gh-readonly-queue/next/pr-15000-c51485c507bcf668c6e55129eb2c1794af4a0732 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 13 11:35:05 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15000_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
11:35:09 [11:35:09.910]
INFO:
prover-client:proving-agent:job-controller-388c3823 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.921]
INFO:
prover-client:proving-agent:job-controller-7838b395 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.926]
INFO:
prover-client:proving-agent:job-controller-3ec263e8 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.928]
WARN:
prover-client:proving-agent:job-controller-3ec263e8 Aborted job controller for jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.928]
WARN:
prover-client:proving-agent:job-controller-3ec263e8 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:35:09 [11:35:09.934]
INFO:
prover-client:proving-agent:job-controller-3f41895c Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.938]
INFO:
prover-client:proving-agent:job-controller-66f67492 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.944]
INFO:
prover-client:proving-agent:job-controller-bdca32c9 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.945]
WARN:
prover-client:proving-agent:job-controller-bdca32c9 On complete handler error: Error: test error
{"jobId":"1"}
11:35:09 [11:35:09.948]
INFO:
prover-client:proving-agent:job-controller-7f3fb355 Job controller started jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.950]
WARN:
prover-client:proving-agent:job-controller-7f3fb355 Aborted job controller for jobId=1
{"jobId":"1"}
11:35:09 [11:35:09.954]
WARN:
prover-client:proving-agent:job-controller-7f3fb355 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:35:09
PASS src/proving_broker/proving_job_controller.test.ts
11:35:09 ProvingJobController
11:35:09
✓ reports IDLE status initially (5 ms)
11:35:09
✓ reports PROVING status while busy (13 ms)
11:35:09
✓ reports DONE status after job is done (5 ms)
11:35:09
✓ reports aborted error after cancellation (7 ms)
11:35:09
✓ calls onComplete (7 ms)
11:35:09
✓ calls onComplete with the error (3 ms)
11:35:09
✓ does not crash if onComplete throws (6 ms)
11:35:09
✓ calls onComplete if abort is called but result is masked (8 ms)
11:35:09
11:35:09
Test Suites: 1 passed, 1 total
11:35:09
Tests: 8 passed, 8 total
11:35:09
Snapshots: 0 total
11:35:09
Time: 2.998 s
11:35:09
Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i
.
11:35:09
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?