Parent Log: http://ci.aztec-labs.com/dd99e75a6da3da84 Command: 53a3eb771435c939 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/6e3848bbd6845559b55825f0bc64df0673272969 Env: REF_NAME=gh-readonly-queue/next/pr-15167-bae1f0ed01e43b291f60c0888e05ceb15d4bb6f6 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 09:38:18 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15167_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 09:38:22 [09:38:22.250] INFO: prover-client:proving-agent:job-controller-8e61c099 Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.259] INFO: prover-client:proving-agent:job-controller-9f32109b Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.291] INFO: prover-client:proving-agent:job-controller-3706bad4 Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.292] WARN: prover-client:proving-agent:job-controller-3706bad4 Aborted job controller for jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.293] WARN: prover-client:proving-agent:job-controller-3706bad4 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 09:38:22 [09:38:22.298] INFO: prover-client:proving-agent:job-controller-202dc94e Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.303] INFO: prover-client:proving-agent:job-controller-905d3540 Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.308] INFO: prover-client:proving-agent:job-controller-3c973e7e Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.308] WARN: prover-client:proving-agent:job-controller-3c973e7e On complete handler error: Error: test error {"jobId":"1"} 09:38:22 [09:38:22.311] INFO: prover-client:proving-agent:job-controller-43e3de0e Job controller started jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.313] WARN: prover-client:proving-agent:job-controller-43e3de0e Aborted job controller for jobId=1 {"jobId":"1"} 09:38:22 [09:38:22.315] WARN: prover-client:proving-agent:job-controller-43e3de0e Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 09:38:22 PASS src/proving_broker/proving_job_controller.test.ts 09:38:22 ProvingJobController 09:38:22 ✓ reports IDLE status initially (6 ms) 09:38:22 ✓ reports PROVING status while busy (10 ms) 09:38:22 ✓ reports DONE status after job is done (32 ms) 09:38:22 ✓ reports aborted error after cancellation (6 ms) 09:38:22 ✓ calls onComplete (5 ms) 09:38:22 ✓ calls onComplete with the error (3 ms) 09:38:22 ✓ does not crash if onComplete throws (4 ms) 09:38:22 ✓ calls onComplete if abort is called but result is masked (6 ms) 09:38:22 09:38:22 Test Suites: 1 passed, 1 total 09:38:22 Tests: 8 passed, 8 total 09:38:22 Snapshots: 0 total 09:38:22 Time: 3.304 s 09:38:22 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 09:38:22 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?