Parent Log: http://ci.aztec-labs.com/f97bdeeb954e1abb Command: 17e0d785507e6983 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/5867520ed258adecfee692b3694d693b2c7964ca Env: REF_NAME=gh-readonly-queue/next/pr-14770-9b801754ba98479ee645488c29d2fda1eecbfd85 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 21:51:32 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14770_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 21:51:36 [21:51:36.783] INFO: prover-client:proving-agent:job-controller-c3098611 Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.793] INFO: prover-client:proving-agent:job-controller-c9615013 Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.822] INFO: prover-client:proving-agent:job-controller-af53b09e Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.823] WARN: prover-client:proving-agent:job-controller-af53b09e Aborted job controller for jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.824] WARN: prover-client:proving-agent:job-controller-af53b09e Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:51:36 [21:51:36.830] INFO: prover-client:proving-agent:job-controller-e69637fe Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.835] INFO: prover-client:proving-agent:job-controller-4e06b831 Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.840] INFO: prover-client:proving-agent:job-controller-fea5683b Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.841] WARN: prover-client:proving-agent:job-controller-fea5683b On complete handler error: Error: test error {"jobId":"1"} 21:51:36 [21:51:36.843] INFO: prover-client:proving-agent:job-controller-1b0a1cc6 Job controller started jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.845] WARN: prover-client:proving-agent:job-controller-1b0a1cc6 Aborted job controller for jobId=1 {"jobId":"1"} 21:51:36 [21:51:36.848] WARN: prover-client:proving-agent:job-controller-1b0a1cc6 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:51:36 PASS src/proving_broker/proving_job_controller.test.ts 21:51:36 ProvingJobController 21:51:36 reports IDLE status initially (5 ms) 21:51:36 reports PROVING status while busy (12 ms) 21:51:36 reports DONE status after job is done (28 ms) 21:51:36 reports aborted error after cancellation (6 ms) 21:51:36 calls onComplete (7 ms) 21:51:36 calls onComplete with the error (3 ms) 21:51:36 does not crash if onComplete throws (5 ms) 21:51:36 calls onComplete if abort is called but result is masked (7 ms) 21:51:36 21:51:36 Test Suites: 1 passed, 1 total 21:51:36 Tests: 8 passed, 8 total 21:51:36 Snapshots: 0 total 21:51:36 Time: 3.486 s 21:51:36 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 21:51:36 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?