Parent Log: http://ci.aztec-labs.com/af1e20c8fae4f49c Command: a668859b212fc7b1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3c1b9d57eadcc8fb03a7ed42610cf0a1ae4a32eb Env: REF_NAME=gh-readonly-queue/next/pr-14858-4b0e4dc09fa55f0bc808fa0c7c3e95e8fa997069 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 21:40:10 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14858_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 21:40:15 [21:40:15.152] INFO: prover-client:proving-agent:job-controller-fefd00fd Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.162] INFO: prover-client:proving-agent:job-controller-0ead3c3e Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.198] INFO: prover-client:proving-agent:job-controller-89086ff3 Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.199] WARN: prover-client:proving-agent:job-controller-89086ff3 Aborted job controller for jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.199] WARN: prover-client:proving-agent:job-controller-89086ff3 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:40:15 [21:40:15.206] INFO: prover-client:proving-agent:job-controller-93144d59 Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.210] INFO: prover-client:proving-agent:job-controller-c352f9f8 Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.216] INFO: prover-client:proving-agent:job-controller-952dc790 Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.217] WARN: prover-client:proving-agent:job-controller-952dc790 On complete handler error: Error: test error {"jobId":"1"} 21:40:15 [21:40:15.220] INFO: prover-client:proving-agent:job-controller-40c3b309 Job controller started jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.222] WARN: prover-client:proving-agent:job-controller-40c3b309 Aborted job controller for jobId=1 {"jobId":"1"} 21:40:15 [21:40:15.227] WARN: prover-client:proving-agent:job-controller-40c3b309 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:40:15 PASS src/proving_broker/proving_job_controller.test.ts 21:40:15 ProvingJobController 21:40:15 reports IDLE status initially (6 ms) 21:40:15 reports PROVING status while busy (12 ms) 21:40:15 reports DONE status after job is done (35 ms) 21:40:15 reports aborted error after cancellation (7 ms) 21:40:15 calls onComplete (7 ms) 21:40:15 calls onComplete with the error (3 ms) 21:40:15 does not crash if onComplete throws (6 ms) 21:40:15 calls onComplete if abort is called but result is masked (9 ms) 21:40:15 21:40:15 Test Suites: 1 passed, 1 total 21:40:15 Tests: 8 passed, 8 total 21:40:15 Snapshots: 0 total 21:40:15 Time: 3.83 s 21:40:15 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 21:40:15 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?