Parent Log: http://ci.aztec-labs.com/4829924e1f2af3e5 Command: a01b491a8c032117 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/60e60f99f2634ad75a76b6e103858ff9ccd041d5 Env: REF_NAME=gh-readonly-queue/next/pr-15081-58b067708e8ff927bf26b2994203134853a7eb71 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 18:29:19 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15081_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 18:29:24 [18:29:24.714] INFO: prover-client:proving-agent:job-controller-2def31c6 Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.721] INFO: prover-client:proving-agent:job-controller-b3148bcd Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.733] INFO: prover-client:proving-agent:job-controller-13464026 Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.734] WARN: prover-client:proving-agent:job-controller-13464026 Aborted job controller for jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.734] WARN: prover-client:proving-agent:job-controller-13464026 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 18:29:24 [18:29:24.739] INFO: prover-client:proving-agent:job-controller-8e7c9973 Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.742] INFO: prover-client:proving-agent:job-controller-f1bd42b4 Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.747] INFO: prover-client:proving-agent:job-controller-ec2f3cd5 Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.748] WARN: prover-client:proving-agent:job-controller-ec2f3cd5 On complete handler error: Error: test error {"jobId":"1"} 18:29:24 [18:29:24.750] INFO: prover-client:proving-agent:job-controller-65aa1dda Job controller started jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.751] WARN: prover-client:proving-agent:job-controller-65aa1dda Aborted job controller for jobId=1 {"jobId":"1"} 18:29:24 [18:29:24.756] WARN: prover-client:proving-agent:job-controller-65aa1dda Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 18:29:24 PASS src/proving_broker/proving_job_controller.test.ts 18:29:24 ProvingJobController 18:29:24 ✓ reports IDLE status initially (4 ms) 18:29:24 ✓ reports PROVING status while busy (10 ms) 18:29:24 ✓ reports DONE status after job is done (12 ms) 18:29:24 ✓ reports aborted error after cancellation (5 ms) 18:29:24 ✓ calls onComplete (5 ms) 18:29:24 ✓ calls onComplete with the error (2 ms) 18:29:24 ✓ does not crash if onComplete throws (4 ms) 18:29:24 ✓ calls onComplete if abort is called but result is masked (8 ms) 18:29:24 18:29:24 Test Suites: 1 passed, 1 total 18:29:24 Tests: 8 passed, 8 total 18:29:24 Snapshots: 0 total 18:29:24 Time: 3.627 s 18:29:24 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 18:29:24 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?