Parent Log: http://ci.aztec-labs.com/9b6e09886228f6bb 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:11 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15232_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 13:51:16 [13:51:16.315] INFO: prover-client:proving-agent:job-controller-abd7c651 Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.325] INFO: prover-client:proving-agent:job-controller-eafdcd72 Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.340] INFO: prover-client:proving-agent:job-controller-35917bc6 Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.341] WARN: prover-client:proving-agent:job-controller-35917bc6 Aborted job controller for jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.341] WARN: prover-client:proving-agent:job-controller-35917bc6 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:51:16 [13:51:16.352] INFO: prover-client:proving-agent:job-controller-284e3290 Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.355] INFO: prover-client:proving-agent:job-controller-07f98715 Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.360] INFO: prover-client:proving-agent:job-controller-c29de0bf Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.361] WARN: prover-client:proving-agent:job-controller-c29de0bf On complete handler error: Error: test error {"jobId":"1"} 13:51:16 [13:51:16.362] INFO: prover-client:proving-agent:job-controller-6a44613a Job controller started jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.364] WARN: prover-client:proving-agent:job-controller-6a44613a Aborted job controller for jobId=1 {"jobId":"1"} 13:51:16 [13:51:16.371] WARN: prover-client:proving-agent:job-controller-6a44613a Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:51:16 PASS src/proving_broker/proving_job_controller.test.ts 13:51:16 ProvingJobController 13:51:16 reports IDLE status initially (4 ms) 13:51:16 reports PROVING status while busy (9 ms) 13:51:16 reports DONE status after job is done (15 ms) 13:51:16 reports aborted error after cancellation (13 ms) 13:51:16 calls onComplete (4 ms) 13:51:16 calls onComplete with the error (2 ms) 13:51:16 does not crash if onComplete throws (5 ms) 13:51:16 calls onComplete if abort is called but result is masked (10 ms) 13:51:16 13:51:16 Test Suites: 1 passed, 1 total 13:51:16 Tests: 8 passed, 8 total 13:51:16 Snapshots: 0 total 13:51:16 Time: 3.642 s 13:51:16 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 13:51:16 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?