Parent Log: http://ci.aztec-labs.com/ad41d2c01b79593b Command: 21081b81c02e2d2a yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/c06f30929f18b85bcea93c0926a8d640a3819f00 Env: REF_NAME=gh-readonly-queue/master/pr-15074-2707ec99de02004f3e30e7af0810e0d741ab9794 CURRENT_VERSION=0.87.8 CI_FULL=1 Date: Mon Jun 16 16:21:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15074_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_master 16:21:40 [16:21:40.113] INFO: prover-client:proving-agent:job-controller-bc5da1c5 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.123] INFO: prover-client:proving-agent:job-controller-f44588f9 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.142] INFO: prover-client:proving-agent:job-controller-4bb7ea49 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.144] WARN: prover-client:proving-agent:job-controller-4bb7ea49 Aborted job controller for jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.145] WARN: prover-client:proving-agent:job-controller-4bb7ea49 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:21:40 [16:21:40.149] INFO: prover-client:proving-agent:job-controller-4484af6e Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.153] INFO: prover-client:proving-agent:job-controller-8d4f9f89 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.155] INFO: prover-client:proving-agent:job-controller-9f7505f8 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.156] WARN: prover-client:proving-agent:job-controller-9f7505f8 On complete handler error: Error: test error {"jobId":"1"} 16:21:40 [16:21:40.157] INFO: prover-client:proving-agent:job-controller-be8da870 Job controller started jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.159] WARN: prover-client:proving-agent:job-controller-be8da870 Aborted job controller for jobId=1 {"jobId":"1"} 16:21:40 [16:21:40.162] WARN: prover-client:proving-agent:job-controller-be8da870 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 16:21:40 PASS src/proving_broker/proving_job_controller.test.ts 16:21:40 ProvingJobController 16:21:40 reports IDLE status initially (4 ms) 16:21:40 reports PROVING status while busy (10 ms) 16:21:40 reports DONE status after job is done (20 ms) 16:21:40 reports aborted error after cancellation (7 ms) 16:21:40 calls onComplete (6 ms) 16:21:40 calls onComplete with the error (1 ms) 16:21:40 does not crash if onComplete throws (3 ms) 16:21:40 calls onComplete if abort is called but result is masked (7 ms) 16:21:40 16:21:40 Test Suites: 1 passed, 1 total 16:21:40 Tests: 8 passed, 8 total 16:21:40 Snapshots: 0 total 16:21:40 Time: 2.422 s 16:21:40 Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i. 16:21:40 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?