Parent Log:
http://ci.aztec-labs.com/057d5d7c01df7f9b
Command: 7d3a4ee7e143e35a yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/3b5835195491b53670250790b18c14d922718574
Env: REF_NAME=gh-readonly-queue/next/pr-15094-1542a83b8e029762e119474de1725d84a1aee3d2 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 10:25:03 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15094_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:25:07 [10:25:07.642]
INFO:
prover-client:proving-agent:job-controller-99c65e95 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.651]
INFO:
prover-client:proving-agent:job-controller-c0b3cf83 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.664]
INFO:
prover-client:proving-agent:job-controller-4d7985f4 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.665]
WARN:
prover-client:proving-agent:job-controller-4d7985f4 Aborted job controller for jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.666]
WARN:
prover-client:proving-agent:job-controller-4d7985f4 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:25:07 [10:25:07.671]
INFO:
prover-client:proving-agent:job-controller-a5069318 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.677]
INFO:
prover-client:proving-agent:job-controller-972f2719 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.685]
INFO:
prover-client:proving-agent:job-controller-b4a86151 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.687]
WARN:
prover-client:proving-agent:job-controller-b4a86151 On complete handler error: Error: test error
{"jobId":"1"}
10:25:07 [10:25:07.691]
INFO:
prover-client:proving-agent:job-controller-73bee307 Job controller started jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.708]
WARN:
prover-client:proving-agent:job-controller-73bee307 Aborted job controller for jobId=1
{"jobId":"1"}
10:25:07 [10:25:07.713]
WARN:
prover-client:proving-agent:job-controller-73bee307 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:25:07
PASS src/proving_broker/proving_job_controller.test.ts
10:25:07 ProvingJobController
10:25:07
✓ reports IDLE status initially (4 ms)
10:25:07
✓ reports PROVING status while busy (10 ms)
10:25:07
✓ reports DONE status after job is done (13 ms)
10:25:07
✓ reports aborted error after cancellation (7 ms)
10:25:07
✓ calls onComplete (7 ms)
10:25:07
✓ calls onComplete with the error (3 ms)
10:25:07
✓ does not crash if onComplete throws (9 ms)
10:25:07
✓ calls onComplete if abort is called but result is masked (24 ms)
10:25:07
10:25:07
Test Suites: 1 passed, 1 total
10:25:07
Tests: 8 passed, 8 total
10:25:07
Snapshots: 0 total
10:25:07
Time: 3.05 s
10:25:07
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:25:07
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?