Parent Log: http://ci.aztec-labs.com/c342d0a4b7d0a24c Command: 49ac1aef38652cc1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/0f26f87af2947423f556c64f03e0100cbf5136f7 Env: REF_NAME=gh-readonly-queue/next/pr-15273-74eeec5d95106217d3b3f3068853022cef7fa307 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 25 10:57:05 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15273_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 10:57:10 [10:57:10.785] INFO: prover-client:proving-agent:job-controller-2847d258 Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.795] INFO: prover-client:proving-agent:job-controller-2753caae Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.811] INFO: prover-client:proving-agent:job-controller-00f72de1 Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.812] WARN: prover-client:proving-agent:job-controller-00f72de1 Aborted job controller for jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.813] WARN: prover-client:proving-agent:job-controller-00f72de1 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:57:10 [10:57:10.823] INFO: prover-client:proving-agent:job-controller-045854e8 Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.828] INFO: prover-client:proving-agent:job-controller-0628cff2 Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.833] INFO: prover-client:proving-agent:job-controller-385cf01c Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.833] WARN: prover-client:proving-agent:job-controller-385cf01c On complete handler error: Error: test error {"jobId":"1"} 10:57:10 [10:57:10.836] INFO: prover-client:proving-agent:job-controller-540fd1ce Job controller started jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.838] WARN: prover-client:proving-agent:job-controller-540fd1ce Aborted job controller for jobId=1 {"jobId":"1"} 10:57:10 [10:57:10.843] WARN: prover-client:proving-agent:job-controller-540fd1ce Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:57:10 PASS src/proving_broker/proving_job_controller.test.ts 10:57:10 ProvingJobController 10:57:10 ✓ reports IDLE status initially (4 ms) 10:57:10 ✓ reports PROVING status while busy (12 ms) 10:57:10 ✓ reports DONE status after job is done (15 ms) 10:57:10 ✓ reports aborted error after cancellation (11 ms) 10:57:10 ✓ calls onComplete (7 ms) 10:57:10 ✓ calls onComplete with the error (2 ms) 10:57:10 ✓ does not crash if onComplete throws (5 ms) 10:57:10 ✓ calls onComplete if abort is called but result is masked (9 ms) 10:57:10 10:57:10 Test Suites: 1 passed, 1 total 10:57:10 Tests: 8 passed, 8 total 10:57:10 Snapshots: 0 total 10:57:10 Time: 3.999 s 10:57:10 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 10:57:10 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?