Parent Log: http://ci.aztec-labs.com/bbd24c41c3ef4011 Command: 5e456509c4335308 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1b10c7d500621ca2e4c0db764df67f3085beb282 Env: REF_NAME=gh-readonly-queue/next/pr-15229-99e234fe4473771b32124e0402885610a6a3f98a CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 24 10:07:11 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15229_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 10:07:14 [10:07:14.082] INFO: prover-client:proving-agent:job-controller-fd43d341 Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.089] INFO: prover-client:proving-agent:job-controller-80998a8d Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.113] INFO: prover-client:proving-agent:job-controller-e45b0da5 Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.114] WARN: prover-client:proving-agent:job-controller-e45b0da5 Aborted job controller for jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.115] WARN: prover-client:proving-agent:job-controller-e45b0da5 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:07:14 [10:07:14.119] INFO: prover-client:proving-agent:job-controller-1300a41a Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.123] INFO: prover-client:proving-agent:job-controller-d560592b Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.128] INFO: prover-client:proving-agent:job-controller-b8367534 Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.129] WARN: prover-client:proving-agent:job-controller-b8367534 On complete handler error: Error: test error {"jobId":"1"} 10:07:14 [10:07:14.132] INFO: prover-client:proving-agent:job-controller-9627f000 Job controller started jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.132] WARN: prover-client:proving-agent:job-controller-9627f000 Aborted job controller for jobId=1 {"jobId":"1"} 10:07:14 [10:07:14.136] WARN: prover-client:proving-agent:job-controller-9627f000 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:07:14 PASS src/proving_broker/proving_job_controller.test.ts 10:07:14 ProvingJobController 10:07:14 ✓ reports IDLE status initially (4 ms) 10:07:14 ✓ reports PROVING status while busy (9 ms) 10:07:14 ✓ reports DONE status after job is done (25 ms) 10:07:14 ✓ reports aborted error after cancellation (5 ms) 10:07:14 ✓ calls onComplete (6 ms) 10:07:14 ✓ calls onComplete with the error (3 ms) 10:07:14 ✓ does not crash if onComplete throws (4 ms) 10:07:14 ✓ calls onComplete if abort is called but result is masked (6 ms) 10:07:14 10:07:14 Test Suites: 1 passed, 1 total 10:07:14 Tests: 8 passed, 8 total 10:07:14 Snapshots: 0 total 10:07:14 Time: 1.922 s 10:07:14 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 10:07:14 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?