Parent Log:
http://ci.aztec-labs.com/9033354ff6409726
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:13 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15046_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
22:39:18 [22:39:18.737]
INFO:
prover-client:proving-agent:job-controller-9c9d004c Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.748]
INFO:
prover-client:proving-agent:job-controller-79c9bbaa Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.771]
INFO:
prover-client:proving-agent:job-controller-4153fe20 Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.772]
WARN:
prover-client:proving-agent:job-controller-4153fe20 Aborted job controller for jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.773]
WARN:
prover-client:proving-agent:job-controller-4153fe20 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
22:39:18 [22:39:18.779]
INFO:
prover-client:proving-agent:job-controller-edf67131 Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.785]
INFO:
prover-client:proving-agent:job-controller-0223b62e Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.791]
INFO:
prover-client:proving-agent:job-controller-14c39fee Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.791]
WARN:
prover-client:proving-agent:job-controller-14c39fee On complete handler error: Error: test error
{"jobId":"1"}
22:39:18 [22:39:18.795]
INFO:
prover-client:proving-agent:job-controller-0c5fcb4e Job controller started jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.797]
WARN:
prover-client:proving-agent:job-controller-0c5fcb4e Aborted job controller for jobId=1
{"jobId":"1"}
22:39:18 [22:39:18.802]
WARN:
prover-client:proving-agent:job-controller-0c5fcb4e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
22:39:18
PASS src/proving_broker/proving_job_controller.test.ts
22:39:18 ProvingJobController
22:39:18
✓ reports IDLE status initially (6 ms)
22:39:18
✓ reports PROVING status while busy (13 ms)
22:39:18
✓ reports DONE status after job is done (22 ms)
22:39:18
✓ reports aborted error after cancellation (8 ms)
22:39:18
✓ calls onComplete (8 ms)
22:39:18
✓ calls onComplete with the error (3 ms)
22:39:18
✓ does not crash if onComplete throws (6 ms)
22:39:18
✓ calls onComplete if abort is called but result is masked (9 ms)
22:39:18
22:39:18
Test Suites: 1 passed, 1 total
22:39:18
Tests: 8 passed, 8 total
22:39:18
Snapshots: 0 total
22:39:18
Time: 3.792 s
22:39:18
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
22:39:18
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?