Parent Log:
http://ci.aztec-labs.com/03b64479f6843581
Command: f44e1b4f382283e1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/be1fa8aacb33d330cf496352bb1446439e34c51a
Env: REF_NAME=gh-readonly-queue/next/pr-15162-7d1abcb337009939ee47da8445b5fee80f39fb58 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 10:05:08 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15162_amd64_x4-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:05:12 [10:05:12.381]
INFO:
prover-client:proving-agent:job-controller-3962928e Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.391]
INFO:
prover-client:proving-agent:job-controller-aff7254d Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.398]
INFO:
prover-client:proving-agent:job-controller-3d29fbb3 Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.399]
WARN:
prover-client:proving-agent:job-controller-3d29fbb3 Aborted job controller for jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.400]
WARN:
prover-client:proving-agent:job-controller-3d29fbb3 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:05:12 [10:05:12.406]
INFO:
prover-client:proving-agent:job-controller-031f3d01 Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.411]
INFO:
prover-client:proving-agent:job-controller-07a9d5d5 Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.417]
INFO:
prover-client:proving-agent:job-controller-b7f97345 Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.417]
WARN:
prover-client:proving-agent:job-controller-b7f97345 On complete handler error: Error: test error
{"jobId":"1"}
10:05:12 [10:05:12.420]
INFO:
prover-client:proving-agent:job-controller-5e658964 Job controller started jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.422]
WARN:
prover-client:proving-agent:job-controller-5e658964 Aborted job controller for jobId=1
{"jobId":"1"}
10:05:12 [10:05:12.428]
WARN:
prover-client:proving-agent:job-controller-5e658964 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:05:12
PASS src/proving_broker/proving_job_controller.test.ts
10:05:12 ProvingJobController
10:05:12
✓ reports IDLE status initially (5 ms)
10:05:12
✓ reports PROVING status while busy (12 ms)
10:05:12
✓ reports DONE status after job is done (7 ms)
10:05:12
✓ reports aborted error after cancellation (7 ms)
10:05:12
✓ calls onComplete (6 ms)
10:05:12
✓ calls onComplete with the error (3 ms)
10:05:12
✓ does not crash if onComplete throws (6 ms)
10:05:12
✓ calls onComplete if abort is called but result is masked (9 ms)
10:05:12
10:05:12
Test Suites: 1 passed, 1 total
10:05:12
Tests: 8 passed, 8 total
10:05:12
Snapshots: 0 total
10:05:12
Time: 2.943 s
10:05:12
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:05:12
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?