Parent Log: http://ci.aztec-labs.com/0a191b42feca0cf7 Command: 200d11860e478e79 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/00cd67e98e76d3202a0219baf301d59ef4211872 Env: REF_NAME=gh-readonly-queue/next/pr-15040-7339c264ad706420ee9babb0dd1b6ed793e97402 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 15:21:12 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15040_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 15:21:17 [15:21:17.018] INFO: prover-client:proving-agent:job-controller-3a90e524 Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.029] INFO: prover-client:proving-agent:job-controller-65c4c94f Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.039] INFO: prover-client:proving-agent:job-controller-fb0784b3 Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.041] WARN: prover-client:proving-agent:job-controller-fb0784b3 Aborted job controller for jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.041] WARN: prover-client:proving-agent:job-controller-fb0784b3 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:21:17 [15:21:17.045] INFO: prover-client:proving-agent:job-controller-742f2207 Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.049] INFO: prover-client:proving-agent:job-controller-e23bd4a8 Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.053] INFO: prover-client:proving-agent:job-controller-2010cb13 Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.054] WARN: prover-client:proving-agent:job-controller-2010cb13 On complete handler error: Error: test error {"jobId":"1"} 15:21:17 [15:21:17.057] INFO: prover-client:proving-agent:job-controller-18dd412d Job controller started jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.059] WARN: prover-client:proving-agent:job-controller-18dd412d Aborted job controller for jobId=1 {"jobId":"1"} 15:21:17 [15:21:17.063] WARN: prover-client:proving-agent:job-controller-18dd412d Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:21:17 PASS src/proving_broker/proving_job_controller.test.ts 15:21:17 ProvingJobController 15:21:17 reports IDLE status initially (4 ms) 15:21:17 reports PROVING status while busy (12 ms) 15:21:17 reports DONE status after job is done (8 ms) 15:21:17 reports aborted error after cancellation (8 ms) 15:21:17 calls onComplete (5 ms) 15:21:17 calls onComplete with the error (3 ms) 15:21:17 does not crash if onComplete throws (4 ms) 15:21:17 calls onComplete if abort is called but result is masked (15 ms) 15:21:17 15:21:17 Test Suites: 1 passed, 1 total 15:21:17 Tests: 8 passed, 8 total 15:21:17 Snapshots: 0 total 15:21:17 Time: 3.54 s 15:21:17 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 15:21:17 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?