Parent Log: http://ci.aztec-labs.com/8a3ee89ab285e396 Command: 270716767bef7882 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1c2c2ee2949dbe31742cc9501a31bf3bce8083cf Env: REF_NAME=gh-readonly-queue/next/pr-15232-aedcee89a2544b0e6baf93c4e71d88991f09111e CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 13:51:16 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15232_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 13:51:21 [13:51:21.278] INFO: prover-client:proving-agent:job-controller-e2c308af Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.308] INFO: prover-client:proving-agent:job-controller-15a787eb Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.324] INFO: prover-client:proving-agent:job-controller-664a568c Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.325] WARN: prover-client:proving-agent:job-controller-664a568c Aborted job controller for jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.326] WARN: prover-client:proving-agent:job-controller-664a568c Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:51:21 [13:51:21.331] INFO: prover-client:proving-agent:job-controller-5068b814 Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.335] INFO: prover-client:proving-agent:job-controller-26ee4eaf Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.341] INFO: prover-client:proving-agent:job-controller-7e4cb323 Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.342] WARN: prover-client:proving-agent:job-controller-7e4cb323 On complete handler error: Error: test error {"jobId":"1"} 13:51:21 [13:51:21.344] INFO: prover-client:proving-agent:job-controller-f13eddae Job controller started jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.345] WARN: prover-client:proving-agent:job-controller-f13eddae Aborted job controller for jobId=1 {"jobId":"1"} 13:51:21 [13:51:21.349] WARN: prover-client:proving-agent:job-controller-f13eddae Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:51:21 PASS src/proving_broker/proving_job_controller.test.ts 13:51:21 ProvingJobController 13:51:21 ✓ reports IDLE status initially (5 ms) 13:51:21 ✓ reports PROVING status while busy (23 ms) 13:51:21 ✓ reports DONE status after job is done (18 ms) 13:51:21 ✓ reports aborted error after cancellation (6 ms) 13:51:21 ✓ calls onComplete (7 ms) 13:51:21 ✓ calls onComplete with the error (3 ms) 13:51:21 ✓ does not crash if onComplete throws (5 ms) 13:51:21 ✓ calls onComplete if abort is called but result is masked (7 ms) 13:51:21 13:51:21 Test Suites: 1 passed, 1 total 13:51:21 Tests: 8 passed, 8 total 13:51:21 Snapshots: 0 total 13:51:21 Time: 3.699 s 13:51:21 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 13:51:21 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?