Parent Log: http://ci.aztec-labs.com/5dedeee27fb005f9 Command: 1f475c5d66a44412 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/e56baa7f24bac54baf9e2f22f6f33ae6fa8b8c0f Env: REF_NAME=gh-readonly-queue/next/pr-14891-76ca48a2187e3506bb464eae574e49476c2876ca CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Fri Jun 13 19:22:30 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14891_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 19:22:32 [19:22:32.971] INFO: prover-client:proving-agent:job-controller-50cc2855 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.978] INFO: prover-client:proving-agent:job-controller-e2ef5ac2 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.984] INFO: prover-client:proving-agent:job-controller-f020b231 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.985] WARN: prover-client:proving-agent:job-controller-f020b231 Aborted job controller for jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.985] WARN: prover-client:proving-agent:job-controller-f020b231 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:22:32 [19:22:32.989] INFO: prover-client:proving-agent:job-controller-47853c99 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.993] INFO: prover-client:proving-agent:job-controller-494b8972 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.998] INFO: prover-client:proving-agent:job-controller-5db505b4 Job controller started jobId=1 {"jobId":"1"} 19:22:32 [19:22:32.998] WARN: prover-client:proving-agent:job-controller-5db505b4 On complete handler error: Error: test error {"jobId":"1"} 19:22:33 [19:22:33.001] INFO: prover-client:proving-agent:job-controller-6cd0888f Job controller started jobId=1 {"jobId":"1"} 19:22:33 [19:22:33.003] WARN: prover-client:proving-agent:job-controller-6cd0888f Aborted job controller for jobId=1 {"jobId":"1"} 19:22:33 [19:22:33.006] WARN: prover-client:proving-agent:job-controller-6cd0888f Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:22:33 PASS src/proving_broker/proving_job_controller.test.ts 19:22:33 ProvingJobController 19:22:33 reports IDLE status initially (6 ms) 19:22:33 reports PROVING status while busy (9 ms) 19:22:33 reports DONE status after job is done (5 ms) 19:22:33 reports aborted error after cancellation (4 ms) 19:22:33 calls onComplete (5 ms) 19:22:33 calls onComplete with the error (3 ms) 19:22:33 does not crash if onComplete throws (4 ms) 19:22:33 calls onComplete if abort is called but result is masked (6 ms) 19:22:33 19:22:33 Test Suites: 1 passed, 1 total 19:22:33 Tests: 8 passed, 8 total 19:22:33 Snapshots: 0 total 19:22:33 Time: 1.77 s 19:22:33 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 19:22:33 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?