Parent Log:
http://ci.aztec-labs.com/5c64f73239d8b492
Command: 3b26b88555004035 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/9cf4a24266245fa3ca003adb00e8ae759880c107
Env: REF_NAME=gh-readonly-queue/next/pr-14963-eeab628a4e44477cb6796c5a461ee0c0bb332d75 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 17:10:15 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14963_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
17:10:20 [17:10:20.734]
INFO:
prover-client:proving-agent:job-controller-46a74f90 Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.745]
INFO:
prover-client:proving-agent:job-controller-109fcccf Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.777]
INFO:
prover-client:proving-agent:job-controller-4c74a3dd Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.779]
WARN:
prover-client:proving-agent:job-controller-4c74a3dd Aborted job controller for jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.780]
WARN:
prover-client:proving-agent:job-controller-4c74a3dd Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:10:20 [17:10:20.787]
INFO:
prover-client:proving-agent:job-controller-54a8ad97 Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.794]
INFO:
prover-client:proving-agent:job-controller-27dd640a Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.809]
INFO:
prover-client:proving-agent:job-controller-e990164f Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.810]
WARN:
prover-client:proving-agent:job-controller-e990164f On complete handler error: Error: test error
{"jobId":"1"}
17:10:20 [17:10:20.812]
INFO:
prover-client:proving-agent:job-controller-2c456c98 Job controller started jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.815]
WARN:
prover-client:proving-agent:job-controller-2c456c98 Aborted job controller for jobId=1
{"jobId":"1"}
17:10:20 [17:10:20.819]
WARN:
prover-client:proving-agent:job-controller-2c456c98 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
17:10:20
PASS src/proving_broker/proving_job_controller.test.ts
17:10:20 ProvingJobController
17:10:20
✓ reports IDLE status initially (5 ms)
17:10:20
✓ reports PROVING status while busy (10 ms)
17:10:20
✓ reports DONE status after job is done (31 ms)
17:10:20
✓ reports aborted error after cancellation (9 ms)
17:10:20
✓ calls onComplete (9 ms)
17:10:20
✓ calls onComplete with the error (11 ms)
17:10:20
✓ does not crash if onComplete throws (7 ms)
17:10:20
✓ calls onComplete if abort is called but result is masked (8 ms)
17:10:20
17:10:20
Test Suites: 1 passed, 1 total
17:10:20
Tests: 8 passed, 8 total
17:10:20
Snapshots: 0 total
17:10:20
Time: 4.308 s
17:10:20
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
17:10:20
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?