Parent Log:
http://ci.aztec-labs.com/f92f0e17b07b44aa
Command: 4cadf2b318302dc1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/4bc54c2acb532388aae32aea2765a66709edfdc9
Env: REF_NAME=gh-readonly-queue/next/pr-15249-4873eb2f8189ef2d21a8b7fcfbfebe4dbc0f4145 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 25 20:09:26 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15249_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
20:09:30 [20:09:30.423]
INFO:
prover-client:proving-agent:job-controller-e5b829b6 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.434]
INFO:
prover-client:proving-agent:job-controller-739f4396 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.459]
INFO:
prover-client:proving-agent:job-controller-da974ec4 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.460]
WARN:
prover-client:proving-agent:job-controller-da974ec4 Aborted job controller for jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.461]
WARN:
prover-client:proving-agent:job-controller-da974ec4 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:09:30 [20:09:30.465]
INFO:
prover-client:proving-agent:job-controller-324a226b Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.470]
INFO:
prover-client:proving-agent:job-controller-143c0952 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.477]
INFO:
prover-client:proving-agent:job-controller-90abe3b3 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.478]
WARN:
prover-client:proving-agent:job-controller-90abe3b3 On complete handler error: Error: test error
{"jobId":"1"}
20:09:30 [20:09:30.481]
INFO:
prover-client:proving-agent:job-controller-fcc3ef34 Job controller started jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.483]
WARN:
prover-client:proving-agent:job-controller-fcc3ef34 Aborted job controller for jobId=1
{"jobId":"1"}
20:09:30 [20:09:30.488]
WARN:
prover-client:proving-agent:job-controller-fcc3ef34 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:09:30
PASS src/proving_broker/proving_job_controller.test.ts
20:09:30 ProvingJobController
20:09:30
✓ reports IDLE status initially (5 ms)
20:09:30
✓ reports PROVING status while busy (11 ms)
20:09:30
✓ reports DONE status after job is done (26 ms)
20:09:30
✓ reports aborted error after cancellation (5 ms)
20:09:30
✓ calls onComplete (5 ms)
20:09:30
✓ calls onComplete with the error (3 ms)
20:09:30
✓ does not crash if onComplete throws (7 ms)
20:09:30
✓ calls onComplete if abort is called but result is masked (11 ms)
20:09:30
20:09:30
Test Suites: 1 passed, 1 total
20:09:30
Tests: 8 passed, 8 total
20:09:30
Snapshots: 0 total
20:09:30
Time: 3.211 s
20:09:30
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
20:09:30
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?