Parent Log: http://ci.aztec-labs.com/66a4a534a6c10a99 Command: cbdd76383a795445 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9ba478709ce5c48099f79f9531da8292811cb18a Env: REF_NAME=gh-readonly-queue/staging/pr-15247-3863bc02d671057d0cffd4ced17ca317788ff190 CURRENT_VERSION=1.0.0 CI_FULL=0 Date: Tue Jun 24 15:04:28 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15247_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_staging 15:04:31 [15:04:31.096] INFO: prover-client:proving-agent:job-controller-08a82e7e Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.104] INFO: prover-client:proving-agent:job-controller-f5d522b5 Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.129] INFO: prover-client:proving-agent:job-controller-a11df71b Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.130] WARN: prover-client:proving-agent:job-controller-a11df71b Aborted job controller for jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.130] WARN: prover-client:proving-agent:job-controller-a11df71b Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:04:31 [15:04:31.134] INFO: prover-client:proving-agent:job-controller-d6905072 Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.139] INFO: prover-client:proving-agent:job-controller-8514880d Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.144] INFO: prover-client:proving-agent:job-controller-4220a071 Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.144] WARN: prover-client:proving-agent:job-controller-4220a071 On complete handler error: Error: test error {"jobId":"1"} 15:04:31 [15:04:31.147] INFO: prover-client:proving-agent:job-controller-9ef6d1c9 Job controller started jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.148] WARN: prover-client:proving-agent:job-controller-9ef6d1c9 Aborted job controller for jobId=1 {"jobId":"1"} 15:04:31 [15:04:31.152] WARN: prover-client:proving-agent:job-controller-9ef6d1c9 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 15:04:31 PASS src/proving_broker/proving_job_controller.test.ts 15:04:31 ProvingJobController 15:04:31 reports IDLE status initially (4 ms) 15:04:31 reports PROVING status while busy (9 ms) 15:04:31 reports DONE status after job is done (25 ms) 15:04:31 reports aborted error after cancellation (5 ms) 15:04:31 calls onComplete (5 ms) 15:04:31 calls onComplete with the error (3 ms) 15:04:31 does not crash if onComplete throws (5 ms) 15:04:31 calls onComplete if abort is called but result is masked (6 ms) 15:04:31 15:04:31 Test Suites: 1 passed, 1 total 15:04:31 Tests: 8 passed, 8 total 15:04:31 Snapshots: 0 total 15:04:31 Time: 1.93 s 15:04:31 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 15:04:31 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?