Parent Log: http://ci.aztec-labs.com/b19cd8e5b38225d7 Command: f1d5df06d37e0c0f yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/5c77169d7f01a9e15bc19b05fa231fd96111d7dd Env: REF_NAME=gh-readonly-queue/next/pr-15042-d5c48d855d83e19712c6b72281801c6fce176ec1 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 15:01:37 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 15:01:42 [15:01:42.136] INFO: prover-client:proving-agent:job-controller-01c96e34 Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.146] INFO: prover-client:proving-agent:job-controller-e512a702 Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.178] INFO: prover-client:proving-agent:job-controller-9435eee0 Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.179] WARN: prover-client:proving-agent:job-controller-9435eee0 Aborted job controller for jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.180] WARN: prover-client:proving-agent:job-controller-9435eee0 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:01:42 [15:01:42.185] INFO: prover-client:proving-agent:job-controller-59f2ccf0 Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.190] INFO: prover-client:proving-agent:job-controller-ec36cd6b Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.194] INFO: prover-client:proving-agent:job-controller-9f3b7142 Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.195] WARN: prover-client:proving-agent:job-controller-9f3b7142 On complete handler error: Error: test error {"jobId":"1"} 15:01:42 [15:01:42.198] INFO: prover-client:proving-agent:job-controller-1268a8cf Job controller started jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.201] WARN: prover-client:proving-agent:job-controller-1268a8cf Aborted job controller for jobId=1 {"jobId":"1"} 15:01:42 [15:01:42.206] WARN: prover-client:proving-agent:job-controller-1268a8cf Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:01:42 PASS src/proving_broker/proving_job_controller.test.ts 15:01:42 ProvingJobController 15:01:42 ✓ reports IDLE status initially (8 ms) 15:01:42 ✓ reports PROVING status while busy (12 ms) 15:01:42 ✓ reports DONE status after job is done (33 ms) 15:01:42 ✓ reports aborted error after cancellation (5 ms) 15:01:42 ✓ calls onComplete (7 ms) 15:01:42 ✓ calls onComplete with the error (2 ms) 15:01:42 ✓ does not crash if onComplete throws (6 ms) 15:01:42 ✓ calls onComplete if abort is called but result is masked (11 ms) 15:01:42 15:01:42 Test Suites: 1 passed, 1 total 15:01:42 Tests: 8 passed, 8 total 15:01:42 Snapshots: 0 total 15:01:42 Time: 3.95 s 15:01:42 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 15:01:42 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?