Parent Log:
http://ci.aztec-labs.com/4dfece09b5e9b3d5
Command: 1c48ff816cf3011e yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/e050b787f6dead84c4ef7e5bdb8dcc8cf81d5f65
Env: REF_NAME=gh-readonly-queue/next/pr-15129-d5c48d855d83e19712c6b72281801c6fce176ec1 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 15:33:07 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15129_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
15:33:12 [15:33:12.234]
INFO:
prover-client:proving-agent:job-controller-62ee5e18 Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.247]
INFO:
prover-client:proving-agent:job-controller-2684f12e Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.260]
INFO:
prover-client:proving-agent:job-controller-5beb173e Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.261]
WARN:
prover-client:proving-agent:job-controller-5beb173e Aborted job controller for jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.261]
WARN:
prover-client:proving-agent:job-controller-5beb173e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
15:33:12 [15:33:12.265]
INFO:
prover-client:proving-agent:job-controller-d5500ed9 Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.269]
INFO:
prover-client:proving-agent:job-controller-13d90d4b Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.273]
INFO:
prover-client:proving-agent:job-controller-079dc785 Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.274]
WARN:
prover-client:proving-agent:job-controller-079dc785 On complete handler error: Error: test error
{"jobId":"1"}
15:33:12 [15:33:12.276]
INFO:
prover-client:proving-agent:job-controller-da44fcfb Job controller started jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.277]
WARN:
prover-client:proving-agent:job-controller-da44fcfb Aborted job controller for jobId=1
{"jobId":"1"}
15:33:12 [15:33:12.281]
WARN:
prover-client:proving-agent:job-controller-da44fcfb Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
15:33:12
PASS src/proving_broker/proving_job_controller.test.ts
15:33:12 ProvingJobController
15:33:12
✓ reports IDLE status initially (7 ms)
15:33:12
✓ reports PROVING status while busy (15 ms)
15:33:12
✓ reports DONE status after job is done (14 ms)
15:33:12
✓ reports aborted error after cancellation (5 ms)
15:33:12
✓ calls onComplete (6 ms)
15:33:12
✓ calls onComplete with the error (3 ms)
15:33:12
✓ does not crash if onComplete throws (4 ms)
15:33:12
✓ calls onComplete if abort is called but result is masked (6 ms)
15:33:12
15:33:12
Test Suites: 1 passed, 1 total
15:33:12
Tests: 8 passed, 8 total
15:33:12
Snapshots: 0 total
15:33:12
Time: 3.522 s
15:33:12
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
15:33:12
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?