Parent Log: http://ci.aztec-labs.com/b356907553fe9b08 Command: c065bf7213f35b7e yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f495236d35f9bb0d1086b7ec79256c2c2b7c98b8 Env: REF_NAME=gh-readonly-queue/staging/pr-15201-f0619dd82429a5973f3e1da8d7eb0877264908e3 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Sat Jun 21 13:26:21 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15201_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_staging 13:26:23 [13:26:23.705] INFO: prover-client:proving-agent:job-controller-d0ebb63c Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.712] INFO: prover-client:proving-agent:job-controller-2e26c6d2 Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.736] INFO: prover-client:proving-agent:job-controller-1ec9aecf Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.737] WARN: prover-client:proving-agent:job-controller-1ec9aecf Aborted job controller for jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.738] WARN: prover-client:proving-agent:job-controller-1ec9aecf Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:26:23 [13:26:23.742] INFO: prover-client:proving-agent:job-controller-6fd308d4 Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.746] INFO: prover-client:proving-agent:job-controller-930f3397 Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.751] INFO: prover-client:proving-agent:job-controller-ae8ee90f Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.752] WARN: prover-client:proving-agent:job-controller-ae8ee90f On complete handler error: Error: test error {"jobId":"1"} 13:26:23 [13:26:23.755] INFO: prover-client:proving-agent:job-controller-f513266d Job controller started jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.756] WARN: prover-client:proving-agent:job-controller-f513266d Aborted job controller for jobId=1 {"jobId":"1"} 13:26:23 [13:26:23.760] WARN: prover-client:proving-agent:job-controller-f513266d Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:26:23 PASS src/proving_broker/proving_job_controller.test.ts 13:26:23 ProvingJobController 13:26:23 reports IDLE status initially (4 ms) 13:26:23 reports PROVING status while busy (8 ms) 13:26:23 reports DONE status after job is done (24 ms) 13:26:23 reports aborted error after cancellation (5 ms) 13:26:23 calls onComplete (6 ms) 13:26:23 calls onComplete with the error (3 ms) 13:26:23 does not crash if onComplete throws (4 ms) 13:26:23 calls onComplete if abort is called but result is masked (7 ms) 13:26:23 13:26:23 Test Suites: 1 passed, 1 total 13:26:23 Tests: 8 passed, 8 total 13:26:23 Snapshots: 0 total 13:26:23 Time: 1.943 s 13:26:23 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 13:26:23 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?