Parent Log:
http://ci.aztec-labs.com/bb2c1907b6b504b7
Command: c198f11d7424b063 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/fa23733be8278348dff0959c8094bcfd89eb44d5
Env: REF_NAME=gh-readonly-queue/next/pr-14929-15c121440ebf929fded7bd0c31960fb154a3fa7a CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Thu Jun 12 10:04:15 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14929_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:04:17 [10:04:17.397]
INFO:
prover-client:proving-agent:job-controller-5eeab6bb Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.404]
INFO:
prover-client:proving-agent:job-controller-011f9485 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.410]
INFO:
prover-client:proving-agent:job-controller-ca17ed11 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.411]
WARN:
prover-client:proving-agent:job-controller-ca17ed11 Aborted job controller for jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.411]
WARN:
prover-client:proving-agent:job-controller-ca17ed11 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:04:17 [10:04:17.415]
INFO:
prover-client:proving-agent:job-controller-b7d812c9 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.419]
INFO:
prover-client:proving-agent:job-controller-9743c058 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.424]
INFO:
prover-client:proving-agent:job-controller-4d8ea495 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.424]
WARN:
prover-client:proving-agent:job-controller-4d8ea495 On complete handler error: Error: test error
{"jobId":"1"}
10:04:17 [10:04:17.427]
INFO:
prover-client:proving-agent:job-controller-2ea740f8 Job controller started jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.429]
WARN:
prover-client:proving-agent:job-controller-2ea740f8 Aborted job controller for jobId=1
{"jobId":"1"}
10:04:17 [10:04:17.433]
WARN:
prover-client:proving-agent:job-controller-2ea740f8 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:04:17
PASS src/proving_broker/proving_job_controller.test.ts
10:04:17 ProvingJobController
10:04:17
✓ reports IDLE status initially (3 ms)
10:04:17
✓ reports PROVING status while busy (12 ms)
10:04:17
✓ reports DONE status after job is done (5 ms)
10:04:17
✓ reports aborted error after cancellation (4 ms)
10:04:17
✓ calls onComplete (5 ms)
10:04:17
✓ calls onComplete with the error (3 ms)
10:04:17
✓ does not crash if onComplete throws (4 ms)
10:04:17
✓ calls onComplete if abort is called but result is masked (6 ms)
10:04:17
10:04:17
Test Suites: 1 passed, 1 total
10:04:17
Tests: 8 passed, 8 total
10:04:17
Snapshots: 0 total
10:04:17
Time: 1.76 s
10:04:17
Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i
.
10:04:17
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?