Parent Log: http://ci.aztec-labs.com/fc1750779ccd7d53 Command: 3f1d1d87da1584d1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/aac426c9418162aeee8162ed45014b9393d605b8 Env: REF_NAME=gh-readonly-queue/next/pr-15051-92d685c3a802eb31897b6f13d28b9ee428c73744 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 06:36:33 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15051_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next 06:36:37 [06:36:37.718] INFO: prover-client:proving-agent:job-controller-ca0e17d5 Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.728] INFO: prover-client:proving-agent:job-controller-ce8ff087 Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.740] INFO: prover-client:proving-agent:job-controller-f26be6a2 Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.741] WARN: prover-client:proving-agent:job-controller-f26be6a2 Aborted job controller for jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.742] WARN: prover-client:proving-agent:job-controller-f26be6a2 Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 06:36:37 [06:36:37.748] INFO: prover-client:proving-agent:job-controller-e130331c Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.751] INFO: prover-client:proving-agent:job-controller-97e0a611 Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.754] INFO: prover-client:proving-agent:job-controller-355a3f60 Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.755] WARN: prover-client:proving-agent:job-controller-355a3f60 On complete handler error: Error: test error {"jobId":"1"} 06:36:37 [06:36:37.757] INFO: prover-client:proving-agent:job-controller-044562af Job controller started jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.758] WARN: prover-client:proving-agent:job-controller-044562af Aborted job controller for jobId=1 {"jobId":"1"} 06:36:37 [06:36:37.762] WARN: prover-client:proving-agent:job-controller-044562af Job controller for jobId=1 completed but job was aborted {"currentStatus":"running","jobId":"1"} 06:36:37 PASS src/proving_broker/proving_job_controller.test.ts 06:36:37 ProvingJobController 06:36:37 reports IDLE status initially (5 ms) 06:36:37 reports PROVING status while busy (13 ms) 06:36:37 reports DONE status after job is done (11 ms) 06:36:37 reports aborted error after cancellation (5 ms) 06:36:37 calls onComplete (6 ms) 06:36:37 calls onComplete with the error (2 ms) 06:36:37 does not crash if onComplete throws (4 ms) 06:36:37 calls onComplete if abort is called but result is masked (7 ms) 06:36:37 06:36:37 Test Suites: 1 passed, 1 total 06:36:37 Tests: 8 passed, 8 total 06:36:37 Snapshots: 0 total 06:36:37 Time: 3.625 s 06:36:37 Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts. 06:36:37 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?