Parent Log: http://ci.aztec-labs.com/5dcd1b40cb4c7fca Command: 7a41fc0e1576329f yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/142e6cd5fbf7371f649078f9d6d08828585c664d Env: REF_NAME=gh-readonly-queue/next/pr-14610-016def8adbfe93f34b41a41f439b146b5318c895 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 12:57:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14610_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 12:57:41 [12:57:41.371] INFO: prover-client:proving-agent:job-controller-7c02edc9 Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.378] INFO: prover-client:proving-agent:job-controller-96b685d3 Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.406] INFO: prover-client:proving-agent:job-controller-6a2ea205 Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.407] WARN: prover-client:proving-agent:job-controller-6a2ea205 Aborted job controller for jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.407] WARN: prover-client:proving-agent:job-controller-6a2ea205 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:57:41 [12:57:41.411] INFO: prover-client:proving-agent:job-controller-554925cd Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.414] INFO: prover-client:proving-agent:job-controller-17ed509b Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.418] INFO: prover-client:proving-agent:job-controller-631dd96e Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.419] WARN: prover-client:proving-agent:job-controller-631dd96e On complete handler error: Error: test error {"jobId":"1"} 12:57:41 [12:57:41.422] INFO: prover-client:proving-agent:job-controller-7c4bd8bc Job controller started jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.423] WARN: prover-client:proving-agent:job-controller-7c4bd8bc Aborted job controller for jobId=1 {"jobId":"1"} 12:57:41 [12:57:41.428] WARN: prover-client:proving-agent:job-controller-7c4bd8bc Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:57:41 PASS src/proving_broker/proving_job_controller.test.ts 12:57:41 ProvingJobController 12:57:41 reports IDLE status initially (4 ms) 12:57:41 reports PROVING status while busy (8 ms) 12:57:41 reports DONE status after job is done (28 ms) 12:57:41 reports aborted error after cancellation (4 ms) 12:57:41 calls onComplete (5 ms) 12:57:41 calls onComplete with the error (3 ms) 12:57:41 does not crash if onComplete throws (5 ms) 12:57:41 calls onComplete if abort is called but result is masked (23 ms) 12:57:41 12:57:41 Test Suites: 1 passed, 1 total 12:57:41 Tests: 8 passed, 8 total 12:57:41 Snapshots: 0 total 12:57:41 Time: 3.473 s 12:57:41 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 12:57:41 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?