Parent Log: http://ci.aztec-labs.com/3faf212eece173a6 Command: 71ec8227227d28e6 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/a45107e7f95b675cb2768b6bcb06483b511141f4 Env: REF_NAME=v1.0.0-nightly.20250613 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 02:50:30 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=v1_0_0-nightly_20250613_amd64_x-nightly Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_v1.0.0-nightly.20250613 02:50:33 [02:50:33.963] INFO: prover-client:proving-agent:job-controller-06177956 Job controller started jobId=1 {"jobId":"1"} 02:50:33 [02:50:33.975] INFO: prover-client:proving-agent:job-controller-132f2cfe Job controller started jobId=1 {"jobId":"1"} 02:50:33 [02:50:33.994] INFO: prover-client:proving-agent:job-controller-5d5ddc65 Job controller started jobId=1 {"jobId":"1"} 02:50:33 [02:50:33.995] WARN: prover-client:proving-agent:job-controller-5d5ddc65 Aborted job controller for jobId=1 {"jobId":"1"} 02:50:33 [02:50:33.996] WARN: prover-client:proving-agent:job-controller-5d5ddc65 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 02:50:34 [02:50:34.004] INFO: prover-client:proving-agent:job-controller-64622f13 Job controller started jobId=1 {"jobId":"1"} 02:50:34 [02:50:34.011] INFO: prover-client:proving-agent:job-controller-3a7fdfbd Job controller started jobId=1 {"jobId":"1"} 02:50:34 [02:50:34.019] INFO: prover-client:proving-agent:job-controller-d9f50e4f Job controller started jobId=1 {"jobId":"1"} 02:50:34 [02:50:34.020] WARN: prover-client:proving-agent:job-controller-d9f50e4f On complete handler error: Error: test error {"jobId":"1"} 02:50:34 [02:50:34.022] INFO: prover-client:proving-agent:job-controller-f3d91d6c Job controller started jobId=1 {"jobId":"1"} 02:50:34 [02:50:34.025] WARN: prover-client:proving-agent:job-controller-f3d91d6c Aborted job controller for jobId=1 {"jobId":"1"} 02:50:34 [02:50:34.030] WARN: prover-client:proving-agent:job-controller-f3d91d6c Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 02:50:34 PASS src/proving_broker/proving_job_controller.test.ts 02:50:34 ProvingJobController 02:50:34 reports IDLE status initially (7 ms) 02:50:34 reports PROVING status while busy (15 ms) 02:50:34 reports DONE status after job is done (19 ms) 02:50:34 reports aborted error after cancellation (8 ms) 02:50:34 calls onComplete (9 ms) 02:50:34 calls onComplete with the error (5 ms) 02:50:34 does not crash if onComplete throws (7 ms) 02:50:34 calls onComplete if abort is called but result is masked (11 ms) 02:50:34 02:50:34 Test Suites: 1 passed, 1 total 02:50:34 Tests: 8 passed, 8 total 02:50:34 Snapshots: 0 total 02:50:34 Time: 3.08 s 02:50:34 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 02:50:34 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?