Parent Log: http://ci.aztec-labs.com/5910880ca7ea8613 Command: c6dc62f84205193f yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3cbe7945c84145b8646cf5cf8fb730b915c0dc93 Env: REF_NAME=gh-readonly-queue/next/pr-15068-254faae7d330e160b14c6eaaa099dc92d4a9cac7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 13:30:40 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15068_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 13:30:45 [13:30:45.656] INFO: prover-client:proving-agent:job-controller-dcade72e Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.666] INFO: prover-client:proving-agent:job-controller-f84e05c6 Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.688] INFO: prover-client:proving-agent:job-controller-3eefc226 Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.689] WARN: prover-client:proving-agent:job-controller-3eefc226 Aborted job controller for jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.690] WARN: prover-client:proving-agent:job-controller-3eefc226 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:30:45 [13:30:45.696] INFO: prover-client:proving-agent:job-controller-4d9c83f0 Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.702] INFO: prover-client:proving-agent:job-controller-a3715fb0 Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.707] INFO: prover-client:proving-agent:job-controller-79c95e9c Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.707] WARN: prover-client:proving-agent:job-controller-79c95e9c On complete handler error: Error: test error {"jobId":"1"} 13:30:45 [13:30:45.711] INFO: prover-client:proving-agent:job-controller-f671c30f Job controller started jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.713] WARN: prover-client:proving-agent:job-controller-f671c30f Aborted job controller for jobId=1 {"jobId":"1"} 13:30:45 [13:30:45.719] WARN: prover-client:proving-agent:job-controller-f671c30f Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:30:45 PASS src/proving_broker/proving_job_controller.test.ts 13:30:45 ProvingJobController 13:30:45 ✓ reports IDLE status initially (5 ms) 13:30:45 ✓ reports PROVING status while busy (14 ms) 13:30:45 ✓ reports DONE status after job is done (21 ms) 13:30:45 ✓ reports aborted error after cancellation (7 ms) 13:30:45 ✓ calls onComplete (8 ms) 13:30:45 ✓ calls onComplete with the error (2 ms) 13:30:45 ✓ does not crash if onComplete throws (7 ms) 13:30:45 ✓ calls onComplete if abort is called but result is masked (10 ms) 13:30:45 13:30:45 Test Suites: 1 passed, 1 total 13:30:45 Tests: 8 passed, 8 total 13:30:45 Snapshots: 0 total 13:30:45 Time: 3.789 s 13:30:45 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 13:30:45 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?