Parent Log: http://ci.aztec-labs.com/bac80ed53a95468a Command: 53e9b8d3e8ba3411 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f4ac84d7ac4041d505399edd8819840bb14d6c9d Env: REF_NAME=gh-readonly-queue/master/pr-15005-b1b65bcdbd44a49fbebe5d2265256dc9466e92be CURRENT_VERSION=0.87.8 CI_FULL=1 Date: Fri Jun 13 17:10:27 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15005_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_master 17:10:29 [17:10:29.776] INFO: prover-client:proving-agent:job-controller-d41f5ff8 Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.786] INFO: prover-client:proving-agent:job-controller-5a9a78e1 Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.791] INFO: prover-client:proving-agent:job-controller-236593a6 Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.792] WARN: prover-client:proving-agent:job-controller-236593a6 Aborted job controller for jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.793] WARN: prover-client:proving-agent:job-controller-236593a6 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 17:10:29 [17:10:29.798] INFO: prover-client:proving-agent:job-controller-0fa0b167 Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.803] INFO: prover-client:proving-agent:job-controller-785c697c Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.809] INFO: prover-client:proving-agent:job-controller-c8e0f022 Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.810] WARN: prover-client:proving-agent:job-controller-c8e0f022 On complete handler error: Error: test error {"jobId":"1"} 17:10:29 [17:10:29.813] INFO: prover-client:proving-agent:job-controller-9f81b95f Job controller started jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.815] WARN: prover-client:proving-agent:job-controller-9f81b95f Aborted job controller for jobId=1 {"jobId":"1"} 17:10:29 [17:10:29.819] WARN: prover-client:proving-agent:job-controller-9f81b95f Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 17:10:29 PASS src/proving_broker/proving_job_controller.test.ts 17:10:29 ProvingJobController 17:10:29 reports IDLE status initially (6 ms) 17:10:29 reports PROVING status while busy (11 ms) 17:10:29 reports DONE status after job is done (5 ms) 17:10:29 reports aborted error after cancellation (5 ms) 17:10:29 calls onComplete (7 ms) 17:10:29 calls onComplete with the error (3 ms) 17:10:29 does not crash if onComplete throws (6 ms) 17:10:29 calls onComplete if abort is called but result is masked (8 ms) 17:10:29 17:10:29 Test Suites: 1 passed, 1 total 17:10:29 Tests: 8 passed, 8 total 17:10:29 Snapshots: 0 total 17:10:29 Time: 2.029 s 17:10:29 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 17:10:29 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?