Parent Log: http://ci.aztec-labs.com/08c315a53e9a1c87 Command: d2a1f586812a792c yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/71fe6b444df8fafa5531226cf458dbd22d2f3ab7 Env: REF_NAME=gh-readonly-queue/master/pr-15117-c06f30929f18b85bcea93c0926a8d640a3819f00 CURRENT_VERSION=0.87.8 CI_FULL=1 Date: Tue Jun 17 19:27:35 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15117_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_master 19:27:38 [19:27:38.392] INFO: prover-client:proving-agent:job-controller-d93496a8 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.401] INFO: prover-client:proving-agent:job-controller-3d182946 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.412] INFO: prover-client:proving-agent:job-controller-f8d0aef7 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.413] WARN: prover-client:proving-agent:job-controller-f8d0aef7 Aborted job controller for jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.414] WARN: prover-client:proving-agent:job-controller-f8d0aef7 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:27:38 [19:27:38.419] INFO: prover-client:proving-agent:job-controller-662ccc86 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.424] INFO: prover-client:proving-agent:job-controller-b07b2646 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.428] INFO: prover-client:proving-agent:job-controller-3e540066 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.429] WARN: prover-client:proving-agent:job-controller-3e540066 On complete handler error: Error: test error {"jobId":"1"} 19:27:38 [19:27:38.432] INFO: prover-client:proving-agent:job-controller-e5dad0b0 Job controller started jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.434] WARN: prover-client:proving-agent:job-controller-e5dad0b0 Aborted job controller for jobId=1 {"jobId":"1"} 19:27:38 [19:27:38.438] WARN: prover-client:proving-agent:job-controller-e5dad0b0 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 19:27:38 PASS src/proving_broker/proving_job_controller.test.ts 19:27:38 ProvingJobController 19:27:38 reports IDLE status initially (4 ms) 19:27:38 reports PROVING status while busy (10 ms) 19:27:38 reports DONE status after job is done (10 ms) 19:27:38 reports aborted error after cancellation (6 ms) 19:27:38 calls onComplete (7 ms) 19:27:38 calls onComplete with the error (2 ms) 19:27:38 does not crash if onComplete throws (5 ms) 19:27:38 calls onComplete if abort is called but result is masked (8 ms) 19:27:38 19:27:38 Test Suites: 1 passed, 1 total 19:27:38 Tests: 8 passed, 8 total 19:27:38 Snapshots: 0 total 19:27:38 Time: 1.998 s 19:27:38 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 19:27:38 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?