Parent Log: http://ci.aztec-labs.com/29098e34bc98632e Command: fb52012d377692f9 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1e338a3fb2e2077f1feaee8b86c42644ff8a5352 Env: REF_NAME=gh-readonly-queue/next/pr-15075-fa4d5ef48c8de52059b5658bbd42e4514386f7db CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:42:14 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15075_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 16:42:18 [16:42:18.777] INFO: prover-client:proving-agent:job-controller-d10e6e6a Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.788] INFO: prover-client:proving-agent:job-controller-57030a6e Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.826] INFO: prover-client:proving-agent:job-controller-38e74021 Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.828] WARN: prover-client:proving-agent:job-controller-38e74021 Aborted job controller for jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.829] WARN: prover-client:proving-agent:job-controller-38e74021 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:42:18 [16:42:18.835] INFO: prover-client:proving-agent:job-controller-4ede2e17 Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.842] INFO: prover-client:proving-agent:job-controller-edcff555 Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.851] INFO: prover-client:proving-agent:job-controller-21943893 Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.853] WARN: prover-client:proving-agent:job-controller-21943893 On complete handler error: Error: test error {"jobId":"1"} 16:42:18 [16:42:18.859] INFO: prover-client:proving-agent:job-controller-c6d090b4 Job controller started jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.862] WARN: prover-client:proving-agent:job-controller-c6d090b4 Aborted job controller for jobId=1 {"jobId":"1"} 16:42:18 [16:42:18.867] WARN: prover-client:proving-agent:job-controller-c6d090b4 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:42:18 PASS src/proving_broker/proving_job_controller.test.ts 16:42:18 ProvingJobController 16:42:18 reports IDLE status initially (5 ms) 16:42:18 reports PROVING status while busy (14 ms) 16:42:18 reports DONE status after job is done (38 ms) 16:42:18 reports aborted error after cancellation (8 ms) 16:42:18 calls onComplete (9 ms) 16:42:18 calls onComplete with the error (5 ms) 16:42:18 does not crash if onComplete throws (11 ms) 16:42:18 calls onComplete if abort is called but result is masked (11 ms) 16:42:18 16:42:18 Test Suites: 1 passed, 1 total 16:42:18 Tests: 8 passed, 8 total 16:42:18 Snapshots: 0 total 16:42:18 Time: 3.451 s 16:42:18 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 16:42:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?