Parent Log: http://ci.aztec-labs.com/b452b423336290e2 Command: bbc5a7ea91d19a83 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/4800d08570523bc1b2a9e8ec0dfb09e326f4689a Env: REF_NAME=gh-readonly-queue/next/pr-14900-d3bba2d69dbc070d51bcd50607354193573876ba CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 13:33:13 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14900_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 13:33:17 [13:33:17.351] INFO: prover-client:proving-agent:job-controller-760bef81 Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.360] INFO: prover-client:proving-agent:job-controller-5d85df46 Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.371] INFO: prover-client:proving-agent:job-controller-492e51d2 Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.372] WARN: prover-client:proving-agent:job-controller-492e51d2 Aborted job controller for jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.373] WARN: prover-client:proving-agent:job-controller-492e51d2 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:33:17 [13:33:17.377] INFO: prover-client:proving-agent:job-controller-0015a27e Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.381] INFO: prover-client:proving-agent:job-controller-a40427c3 Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.385] INFO: prover-client:proving-agent:job-controller-e7967feb Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.386] WARN: prover-client:proving-agent:job-controller-e7967feb On complete handler error: Error: test error {"jobId":"1"} 13:33:17 [13:33:17.388] INFO: prover-client:proving-agent:job-controller-375b3b2e Job controller started jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.390] WARN: prover-client:proving-agent:job-controller-375b3b2e Aborted job controller for jobId=1 {"jobId":"1"} 13:33:17 [13:33:17.394] WARN: prover-client:proving-agent:job-controller-375b3b2e Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 13:33:17 PASS src/proving_broker/proving_job_controller.test.ts 13:33:17 ProvingJobController 13:33:17 reports IDLE status initially (7 ms) 13:33:17 reports PROVING status while busy (11 ms) 13:33:17 reports DONE status after job is done (11 ms) 13:33:17 reports aborted error after cancellation (5 ms) 13:33:17 calls onComplete (6 ms) 13:33:17 calls onComplete with the error (3 ms) 13:33:17 does not crash if onComplete throws (4 ms) 13:33:17 calls onComplete if abort is called but result is masked (8 ms) 13:33:17 13:33:17 Test Suites: 1 passed, 1 total 13:33:17 Tests: 8 passed, 8 total 13:33:17 Snapshots: 0 total 13:33:17 Time: 2.596 s 13:33:17 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 13:33:17 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?