Parent Log: http://ci.aztec-labs.com/7d50fe3fd123434b Command: 9e675ed54321cc5a yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/96a426245731b3f48fcb6dd5e2a683c858706602 Env: REF_NAME=gh-readonly-queue/next/pr-15083-5867520ed258adecfee692b3694d693b2c7964ca CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 21:53:47 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15083_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 21:53:51 [21:53:51.746] INFO: prover-client:proving-agent:job-controller-2b09669a Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.757] INFO: prover-client:proving-agent:job-controller-14c8e1d8 Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.781] INFO: prover-client:proving-agent:job-controller-8b03149b Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.783] WARN: prover-client:proving-agent:job-controller-8b03149b Aborted job controller for jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.783] WARN: prover-client:proving-agent:job-controller-8b03149b Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:53:51 [21:53:51.789] INFO: prover-client:proving-agent:job-controller-3f4ec6a1 Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.794] INFO: prover-client:proving-agent:job-controller-4f6b3fe4 Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.798] INFO: prover-client:proving-agent:job-controller-33d8e51d Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.799] WARN: prover-client:proving-agent:job-controller-33d8e51d On complete handler error: Error: test error {"jobId":"1"} 21:53:51 [21:53:51.801] INFO: prover-client:proving-agent:job-controller-24e045d9 Job controller started jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.803] WARN: prover-client:proving-agent:job-controller-24e045d9 Aborted job controller for jobId=1 {"jobId":"1"} 21:53:51 [21:53:51.807] WARN: prover-client:proving-agent:job-controller-24e045d9 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 21:53:51 PASS src/proving_broker/proving_job_controller.test.ts 21:53:51 ProvingJobController 21:53:51 reports IDLE status initially (5 ms) 21:53:51 reports PROVING status while busy (12 ms) 21:53:51 reports DONE status after job is done (24 ms) 21:53:51 reports aborted error after cancellation (7 ms) 21:53:51 calls onComplete (7 ms) 21:53:51 calls onComplete with the error (2 ms) 21:53:51 does not crash if onComplete throws (4 ms) 21:53:51 calls onComplete if abort is called but result is masked (7 ms) 21:53:51 21:53:51 Test Suites: 1 passed, 1 total 21:53:51 Tests: 8 passed, 8 total 21:53:51 Snapshots: 0 total 21:53:51 Time: 3.303 s 21:53:51 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 21:53:51 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?