Parent Log: http://ci.aztec-labs.com/cc7478688846fa30 Command: c118fea9c063e772 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/12d931e5ea9343eec403068931d3121e1d10e37e Env: REF_NAME=gh-readonly-queue/next/pr-15042-254faae7d330e160b14c6eaaa099dc92d4a9cac7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 12:34:48 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 12:34:52 [12:34:52.231] INFO: prover-client:proving-agent:job-controller-be857bfa Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.250] INFO: prover-client:proving-agent:job-controller-f96a5711 Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.255] INFO: prover-client:proving-agent:job-controller-c4375c3a Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.256] WARN: prover-client:proving-agent:job-controller-c4375c3a Aborted job controller for jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.257] WARN: prover-client:proving-agent:job-controller-c4375c3a Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:34:52 [12:34:52.261] INFO: prover-client:proving-agent:job-controller-82150824 Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.264] INFO: prover-client:proving-agent:job-controller-83b718e3 Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.269] INFO: prover-client:proving-agent:job-controller-93f9872a Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.269] WARN: prover-client:proving-agent:job-controller-93f9872a On complete handler error: Error: test error {"jobId":"1"} 12:34:52 [12:34:52.271] INFO: prover-client:proving-agent:job-controller-729050ab Job controller started jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.272] WARN: prover-client:proving-agent:job-controller-729050ab Aborted job controller for jobId=1 {"jobId":"1"} 12:34:52 [12:34:52.275] WARN: prover-client:proving-agent:job-controller-729050ab Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 12:34:52 PASS src/proving_broker/proving_job_controller.test.ts 12:34:52 ProvingJobController 12:34:52 reports IDLE status initially (11 ms) 12:34:52 reports PROVING status while busy (22 ms) 12:34:52 reports DONE status after job is done (7 ms) 12:34:52 reports aborted error after cancellation (5 ms) 12:34:52 calls onComplete (5 ms) 12:34:52 calls onComplete with the error (3 ms) 12:34:52 does not crash if onComplete throws (4 ms) 12:34:52 calls onComplete if abort is called but result is masked (6 ms) 12:34:52 12:34:52 Test Suites: 1 passed, 1 total 12:34:52 Tests: 8 passed, 8 total 12:34:52 Snapshots: 0 total 12:34:52 Time: 2.414 s 12:34:52 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 12:34:52 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?