Parent Log: http://ci.aztec-labs.com/a23b82fd22ca24f9 Command: d2fcfaaceedeb658 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/bd28eda782eb6f2e1e5c2101a27104b4ad8796b3 Env: REF_NAME=gh-readonly-queue/next/pr-15315-634f8607a18c02c1d6e9ab5f302821fa8fc0e833 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 26 16:33:47 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15315_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 16:33:51 [16:33:51.886] INFO: prover-client:proving-agent:job-controller-b3b4c2ab Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.894] INFO: prover-client:proving-agent:job-controller-e26668ce Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.931] INFO: prover-client:proving-agent:job-controller-7c24dc14 Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.932] WARN: prover-client:proving-agent:job-controller-7c24dc14 Aborted job controller for jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.933] WARN: prover-client:proving-agent:job-controller-7c24dc14 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:33:51 [16:33:51.939] INFO: prover-client:proving-agent:job-controller-a6772146 Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.943] INFO: prover-client:proving-agent:job-controller-05badaf8 Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.947] INFO: prover-client:proving-agent:job-controller-19f16c78 Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.948] WARN: prover-client:proving-agent:job-controller-19f16c78 On complete handler error: Error: test error {"jobId":"1"} 16:33:51 [16:33:51.951] INFO: prover-client:proving-agent:job-controller-5375019b Job controller started jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.953] WARN: prover-client:proving-agent:job-controller-5375019b Aborted job controller for jobId=1 {"jobId":"1"} 16:33:51 [16:33:51.957] WARN: prover-client:proving-agent:job-controller-5375019b Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:33:51 PASS src/proving_broker/proving_job_controller.test.ts 16:33:51 ProvingJobController 16:33:51 reports IDLE status initially (4 ms) 16:33:51 reports PROVING status while busy (9 ms) 16:33:51 reports DONE status after job is done (37 ms) 16:33:51 reports aborted error after cancellation (8 ms) 16:33:51 calls onComplete (6 ms) 16:33:51 calls onComplete with the error (3 ms) 16:33:51 does not crash if onComplete throws (5 ms) 16:33:51 calls onComplete if abort is called but result is masked (6 ms) 16:33:51 16:33:51 Test Suites: 1 passed, 1 total 16:33:51 Tests: 8 passed, 8 total 16:33:51 Snapshots: 0 total 16:33:51 Time: 3.101 s 16:33:51 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 16:33:51 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?