Parent Log: http://ci.aztec-labs.com/f36ae8a6d7e2bbdb Command: 5523e2d7d458c27d yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/21a568ac0c9ef351b1923375be41d4620add2b60 Env: REF_NAME=gh-readonly-queue/next/pr-15042-b80949775e5c27908a6055ad24592f7d98bdc45a CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Sun Jun 15 12:37:17 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15042_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 12:37:20 [12:37:20.345] INFO: prover-client:proving-agent:job-controller-dccbc0f2 Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.352] INFO: prover-client:proving-agent:job-controller-6224ffc9 Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.358] INFO: prover-client:proving-agent:job-controller-a5931b68 Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.358] WARN: prover-client:proving-agent:job-controller-a5931b68 Aborted job controller for jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.359] WARN: prover-client:proving-agent:job-controller-a5931b68 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:37:20 [12:37:20.363] INFO: prover-client:proving-agent:job-controller-15b73166 Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.367] INFO: prover-client:proving-agent:job-controller-f45cab9c Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.371] INFO: prover-client:proving-agent:job-controller-7dbb4e4e Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.371] WARN: prover-client:proving-agent:job-controller-7dbb4e4e On complete handler error: Error: test error {"jobId":"1"} 12:37:20 [12:37:20.374] INFO: prover-client:proving-agent:job-controller-38268000 Job controller started jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.376] WARN: prover-client:proving-agent:job-controller-38268000 Aborted job controller for jobId=1 {"jobId":"1"} 12:37:20 [12:37:20.379] WARN: prover-client:proving-agent:job-controller-38268000 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:37:20 PASS src/proving_broker/proving_job_controller.test.ts 12:37:20 ProvingJobController 12:37:20 reports IDLE status initially (3 ms) 12:37:20 reports PROVING status while busy (9 ms) 12:37:20 reports DONE status after job is done (5 ms) 12:37:20 reports aborted error after cancellation (4 ms) 12:37:20 calls onComplete (6 ms) 12:37:20 calls onComplete with the error (2 ms) 12:37:20 does not crash if onComplete throws (5 ms) 12:37:20 calls onComplete if abort is called but result is masked (7 ms) 12:37:20 12:37:20 Test Suites: 1 passed, 1 total 12:37:20 Tests: 8 passed, 8 total 12:37:20 Snapshots: 0 total 12:37:20 Time: 1.752 s 12:37:20 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 12:37:20 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?