Parent Log:
http://ci.aztec-labs.com/e32b3e81ed0d1d8e
Command: 1a84647d900d18a3 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/484694b997ac4ff62ed6d008cc3f12e0c60720ff
Env: REF_NAME=gh-readonly-queue/next/pr-15077-3c1b9d57eadcc8fb03a7ed42610cf0a1ae4a32eb CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 07:43:10 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15077_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
07:43:16 [07:43:16.038]
INFO:
prover-client:proving-agent:job-controller-f2c937b8 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.048]
INFO:
prover-client:proving-agent:job-controller-cde73744 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.080]
INFO:
prover-client:proving-agent:job-controller-8bd4ff8e Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.081]
WARN:
prover-client:proving-agent:job-controller-8bd4ff8e Aborted job controller for jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.082]
WARN:
prover-client:proving-agent:job-controller-8bd4ff8e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
07:43:16 [07:43:16.087]
INFO:
prover-client:proving-agent:job-controller-43c752e3 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.093]
INFO:
prover-client:proving-agent:job-controller-862bc1c5 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.101]
INFO:
prover-client:proving-agent:job-controller-5087fd89 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.102]
WARN:
prover-client:proving-agent:job-controller-5087fd89 On complete handler error: Error: test error
{"jobId":"1"}
07:43:16 [07:43:16.105]
INFO:
prover-client:proving-agent:job-controller-ab5c3b95 Job controller started jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.106]
WARN:
prover-client:proving-agent:job-controller-ab5c3b95 Aborted job controller for jobId=1
{"jobId":"1"}
07:43:16 [07:43:16.111]
WARN:
prover-client:proving-agent:job-controller-ab5c3b95 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
07:43:16
PASS src/proving_broker/proving_job_controller.test.ts
07:43:16 ProvingJobController
07:43:16
✓ reports IDLE status initially (6 ms)
07:43:16
✓ reports PROVING status while busy (12 ms)
07:43:16
✓ reports DONE status after job is done (31 ms)
07:43:16
✓ reports aborted error after cancellation (6 ms)
07:43:16
✓ calls onComplete (8 ms)
07:43:16
✓ calls onComplete with the error (4 ms)
07:43:16
✓ does not crash if onComplete throws (6 ms)
07:43:16
✓ calls onComplete if abort is called but result is masked (9 ms)
07:43:16
07:43:16
Test Suites: 1 passed, 1 total
07:43:16
Tests: 8 passed, 8 total
07:43:16
Snapshots: 0 total
07:43:16
Time: 4.175 s
07:43:16
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
07:43:16
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?