Parent Log: http://ci.aztec-labs.com/48e451a828b576eb Command: f9856415d54196c8 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3084a7eb89277f14c021ec43f4bddf01c77cc5cc Env: REF_NAME=gh-readonly-queue/next/pr-15077-433ba6218aed45169029991a493e4232b30b8ec6 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 19:12:19 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15077_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 19:12:22 [19:12:22.961] INFO: prover-client:proving-agent:job-controller-253c2969 Job controller started jobId=1 {"jobId":"1"} 19:12:22 [19:12:22.968] INFO: prover-client:proving-agent:job-controller-00ac03da Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.004] INFO: prover-client:proving-agent:job-controller-905f4318 Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.005] WARN: prover-client:proving-agent:job-controller-905f4318 Aborted job controller for jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.005] WARN: prover-client:proving-agent:job-controller-905f4318 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:12:23 [19:12:23.011] INFO: prover-client:proving-agent:job-controller-7ec4eb1f Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.016] INFO: prover-client:proving-agent:job-controller-384d1bc4 Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.021] INFO: prover-client:proving-agent:job-controller-99f909ee Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.022] WARN: prover-client:proving-agent:job-controller-99f909ee On complete handler error: Error: test error {"jobId":"1"} 19:12:23 [19:12:23.024] INFO: prover-client:proving-agent:job-controller-46ac7695 Job controller started jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.026] WARN: prover-client:proving-agent:job-controller-46ac7695 Aborted job controller for jobId=1 {"jobId":"1"} 19:12:23 [19:12:23.030] WARN: prover-client:proving-agent:job-controller-46ac7695 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:12:23 PASS src/proving_broker/proving_job_controller.test.ts 19:12:23 ProvingJobController 19:12:23 reports IDLE status initially (4 ms) 19:12:23 reports PROVING status while busy (8 ms) 19:12:23 reports DONE status after job is done (35 ms) 19:12:23 reports aborted error after cancellation (6 ms) 19:12:23 calls onComplete (7 ms) 19:12:23 calls onComplete with the error (4 ms) 19:12:23 does not crash if onComplete throws (5 ms) 19:12:23 calls onComplete if abort is called but result is masked (8 ms) 19:12:23 19:12:23 Test Suites: 1 passed, 1 total 19:12:23 Tests: 8 passed, 8 total 19:12:23 Snapshots: 0 total 19:12:23 Time: 3.106 s 19:12:23 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 19:12:23 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?