Parent Log:
http://ci.aztec-labs.com/d1d12efbb2463ba0
Command: d2b17a71056754a7 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/b70544b6d50e3ecb6598361f1990bd51745c7b55
Env: REF_NAME=gh-readonly-queue/next/pr-15046-96a426245731b3f48fcb6dd5e2a683c858706602 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 22:39:21 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15046_amd64_x4-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
22:39:27 [22:39:27.367]
INFO:
prover-client:proving-agent:job-controller-7c66ee70 Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.384]
INFO:
prover-client:proving-agent:job-controller-85a16ee5 Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.419]
INFO:
prover-client:proving-agent:job-controller-27ae473f Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.421]
WARN:
prover-client:proving-agent:job-controller-27ae473f Aborted job controller for jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.422]
WARN:
prover-client:proving-agent:job-controller-27ae473f Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
22:39:27 [22:39:27.430]
INFO:
prover-client:proving-agent:job-controller-e1115731 Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.437]
INFO:
prover-client:proving-agent:job-controller-2b9cd0ad Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.446]
INFO:
prover-client:proving-agent:job-controller-5165a0b2 Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.447]
WARN:
prover-client:proving-agent:job-controller-5165a0b2 On complete handler error: Error: test error
{"jobId":"1"}
22:39:27 [22:39:27.451]
INFO:
prover-client:proving-agent:job-controller-6e7bb9ef Job controller started jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.457]
WARN:
prover-client:proving-agent:job-controller-6e7bb9ef Aborted job controller for jobId=1
{"jobId":"1"}
22:39:27 [22:39:27.462]
WARN:
prover-client:proving-agent:job-controller-6e7bb9ef Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
22:39:27
PASS src/proving_broker/proving_job_controller.test.ts
22:39:27 ProvingJobController
22:39:27
✓ reports IDLE status initially (6 ms)
22:39:27
✓ reports PROVING status while busy (15 ms)
22:39:27
✓ reports DONE status after job is done (35 ms)
22:39:27
✓ reports aborted error after cancellation (10 ms)
22:39:27
✓ calls onComplete (9 ms)
22:39:27
✓ calls onComplete with the error (3 ms)
22:39:27
✓ does not crash if onComplete throws (11 ms)
22:39:27
✓ calls onComplete if abort is called but result is masked (14 ms)
22:39:27
22:39:27
Test Suites: 1 passed, 1 total
22:39:27
Tests: 8 passed, 8 total
22:39:27
Snapshots: 0 total
22:39:27
Time: 4.518 s
22:39:27
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
22:39:27
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?