Parent Log: http://ci.aztec-labs.com/ee2cd287ab732702 Command: 73379369dc8552ae yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/73e6175e802437ee93b26885b6aff2fc12640523 Env: REF_NAME=gh-readonly-queue/next/pr-15163-4608046e462faf9ff3fbee265ba34dbecb5d0b31 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 23 14:14:34 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15163_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 14:14:38 [14:14:38.240] INFO: prover-client:proving-agent:job-controller-8a544a2d Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.258] INFO: prover-client:proving-agent:job-controller-8e3c456c Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.272] INFO: prover-client:proving-agent:job-controller-37ead5af Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.273] WARN: prover-client:proving-agent:job-controller-37ead5af Aborted job controller for jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.273] WARN: prover-client:proving-agent:job-controller-37ead5af Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 14:14:38 [14:14:38.278] INFO: prover-client:proving-agent:job-controller-29560783 Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.283] INFO: prover-client:proving-agent:job-controller-8be63369 Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.288] INFO: prover-client:proving-agent:job-controller-a94103f3 Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.289] WARN: prover-client:proving-agent:job-controller-a94103f3 On complete handler error: Error: test error {"jobId":"1"} 14:14:38 [14:14:38.291] INFO: prover-client:proving-agent:job-controller-68110e01 Job controller started jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.293] WARN: prover-client:proving-agent:job-controller-68110e01 Aborted job controller for jobId=1 {"jobId":"1"} 14:14:38 [14:14:38.297] WARN: prover-client:proving-agent:job-controller-68110e01 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 14:14:38 PASS src/proving_broker/proving_job_controller.test.ts 14:14:38 ProvingJobController 14:14:38 reports IDLE status initially (7 ms) 14:14:38 reports PROVING status while busy (14 ms) 14:14:38 reports DONE status after job is done (21 ms) 14:14:38 reports aborted error after cancellation (6 ms) 14:14:38 calls onComplete (6 ms) 14:14:38 calls onComplete with the error (3 ms) 14:14:38 does not crash if onComplete throws (5 ms) 14:14:38 calls onComplete if abort is called but result is masked (7 ms) 14:14:38 14:14:38 Test Suites: 1 passed, 1 total 14:14:38 Tests: 8 passed, 8 total 14:14:38 Snapshots: 0 total 14:14:38 Time: 2.963 s 14:14:38 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 14:14:38 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?