Parent Log: http://ci.aztec-labs.com/680c9782ad4fbb8a Command: 02087f8fc23cff6c yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/78d87cb88633aee537d022d6fd8e57ceb74a3a95 Env: REF_NAME=gh-readonly-queue/next/pr-15024-78a5deb1c3aa24503935bbda20f9374ba35aa5c4 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 10:50:18 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15024_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 10:50:23 [10:50:23.125] INFO: prover-client:proving-agent:job-controller-28bb2c13 Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.135] INFO: prover-client:proving-agent:job-controller-de73212f Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.163] INFO: prover-client:proving-agent:job-controller-f855003e Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.164] WARN: prover-client:proving-agent:job-controller-f855003e Aborted job controller for jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.164] WARN: prover-client:proving-agent:job-controller-f855003e Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:50:23 [10:50:23.169] INFO: prover-client:proving-agent:job-controller-302f93de Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.174] INFO: prover-client:proving-agent:job-controller-8bd9ea63 Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.180] INFO: prover-client:proving-agent:job-controller-92aa3135 Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.180] WARN: prover-client:proving-agent:job-controller-92aa3135 On complete handler error: Error: test error {"jobId":"1"} 10:50:23 [10:50:23.183] INFO: prover-client:proving-agent:job-controller-5033a076 Job controller started jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.184] WARN: prover-client:proving-agent:job-controller-5033a076 Aborted job controller for jobId=1 {"jobId":"1"} 10:50:23 [10:50:23.188] WARN: prover-client:proving-agent:job-controller-5033a076 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:50:23 PASS src/proving_broker/proving_job_controller.test.ts 10:50:23 ProvingJobController 10:50:23 reports IDLE status initially (5 ms) 10:50:23 reports PROVING status while busy (11 ms) 10:50:23 reports DONE status after job is done (27 ms) 10:50:23 reports aborted error after cancellation (7 ms) 10:50:23 calls onComplete (7 ms) 10:50:23 calls onComplete with the error (3 ms) 10:50:23 does not crash if onComplete throws (5 ms) 10:50:23 calls onComplete if abort is called but result is masked (8 ms) 10:50:23 10:50:23 Test Suites: 1 passed, 1 total 10:50:23 Tests: 8 passed, 8 total 10:50:23 Snapshots: 0 total 10:50:23 Time: 3.449 s 10:50:23 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 10:50:23 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?