Parent Log: http://ci.aztec-labs.com/1ad07270fdfb8297 Command: 2dbc0f6449ec2b2d yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/7edf16da6c056f9499e2dfd9c71fb9b7580f9bfc Env: REF_NAME=gh-readonly-queue/next/pr-15215-1b10c7d500621ca2e4c0db764df67f3085beb282 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 24 10:20:39 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15215_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:20:42 [10:20:42.147] INFO: prover-client:proving-agent:job-controller-ddbcebc3 Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.154] INFO: prover-client:proving-agent:job-controller-0b1ff64c Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.179] INFO: prover-client:proving-agent:job-controller-40ec9ef9 Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.180] WARN: prover-client:proving-agent:job-controller-40ec9ef9 Aborted job controller for jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.180] WARN: prover-client:proving-agent:job-controller-40ec9ef9 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:20:42 [10:20:42.184] INFO: prover-client:proving-agent:job-controller-3c93ff10 Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.189] INFO: prover-client:proving-agent:job-controller-0a57cb60 Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.194] INFO: prover-client:proving-agent:job-controller-4be5963a Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.195] WARN: prover-client:proving-agent:job-controller-4be5963a On complete handler error: Error: test error {"jobId":"1"} 10:20:42 [10:20:42.198] INFO: prover-client:proving-agent:job-controller-933ed508 Job controller started jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.199] WARN: prover-client:proving-agent:job-controller-933ed508 Aborted job controller for jobId=1 {"jobId":"1"} 10:20:42 [10:20:42.202] WARN: prover-client:proving-agent:job-controller-933ed508 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 10:20:42 PASS src/proving_broker/proving_job_controller.test.ts 10:20:42 ProvingJobController 10:20:42 reports IDLE status initially (4 ms) 10:20:42 reports PROVING status while busy (9 ms) 10:20:42 reports DONE status after job is done (24 ms) 10:20:42 reports aborted error after cancellation (5 ms) 10:20:42 calls onComplete (6 ms) 10:20:42 calls onComplete with the error (3 ms) 10:20:42 does not crash if onComplete throws (5 ms) 10:20:42 calls onComplete if abort is called but result is masked (6 ms) 10:20:42 10:20:42 Test Suites: 1 passed, 1 total 10:20:42 Tests: 8 passed, 8 total 10:20:42 Snapshots: 0 total 10:20:42 Time: 1.928 s 10:20:42 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 10:20:42 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?