Parent Log:
http://ci.aztec-labs.com/c38ea5f9f89d6d6c
Command: 02087f8fc23cff6c yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/78d87cb88633aee537d022d6fd8e57ceb74a3a95
Env: REF_NAME=gh-readonly-queue/next/pr-15024-78a5deb1c3aa24503935bbda20f9374ba35aa5c4 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 10:49:37 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15024_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:49:42 [10:49:42.975]
INFO:
prover-client:proving-agent:job-controller-d7ffeece Job controller started jobId=1
{"jobId":"1"}
10:49:42 [10:49:42.992]
INFO:
prover-client:proving-agent:job-controller-2f49ca6b Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.018]
INFO:
prover-client:proving-agent:job-controller-f10fa292 Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.020]
WARN:
prover-client:proving-agent:job-controller-f10fa292 Aborted job controller for jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.020]
WARN:
prover-client:proving-agent:job-controller-f10fa292 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:49:43 [10:49:43.026]
INFO:
prover-client:proving-agent:job-controller-f23d8d42 Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.031]
INFO:
prover-client:proving-agent:job-controller-0caf6cf2 Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.036]
INFO:
prover-client:proving-agent:job-controller-9afdb8de Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.037]
WARN:
prover-client:proving-agent:job-controller-9afdb8de On complete handler error: Error: test error
{"jobId":"1"}
10:49:43 [10:49:43.040]
INFO:
prover-client:proving-agent:job-controller-f3eaa350 Job controller started jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.042]
WARN:
prover-client:proving-agent:job-controller-f3eaa350 Aborted job controller for jobId=1
{"jobId":"1"}
10:49:43 [10:49:43.046]
WARN:
prover-client:proving-agent:job-controller-f3eaa350 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:49:43
PASS src/proving_broker/proving_job_controller.test.ts
10:49:43 ProvingJobController
10:49:43
✓ reports IDLE status initially (4 ms)
10:49:43
✓ reports PROVING status while busy (16 ms)
10:49:43
✓ reports DONE status after job is done (28 ms)
10:49:43
✓ reports aborted error after cancellation (5 ms)
10:49:43
✓ calls onComplete (7 ms)
10:49:43
✓ calls onComplete with the error (3 ms)
10:49:43
✓ does not crash if onComplete throws (6 ms)
10:49:43
✓ calls onComplete if abort is called but result is masked (8 ms)
10:49:43
10:49:43
Test Suites: 1 passed, 1 total
10:49:43
Tests: 8 passed, 8 total
10:49:43
Snapshots: 0 total
10:49:43
Time: 4.041 s
10:49:43
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:49:43
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?