Parent Log:
http://ci.aztec-labs.com/a0f0f050e593860b
Command: 4dcaaab13058c9f1 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/1542a83b8e029762e119474de1725d84a1aee3d2
Env: REF_NAME=gh-readonly-queue/next/pr-15095-eb7990c89ac679ce7fdfc2e985670cbf85c04be2 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 10:15:18 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15095_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:15:24 [10:15:24.173]
INFO:
prover-client:proving-agent:job-controller-afde00e7 Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.186]
INFO:
prover-client:proving-agent:job-controller-e131c1f6 Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.203]
INFO:
prover-client:proving-agent:job-controller-4af72e36 Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.204]
WARN:
prover-client:proving-agent:job-controller-4af72e36 Aborted job controller for jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.205]
WARN:
prover-client:proving-agent:job-controller-4af72e36 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:15:24 [10:15:24.208]
INFO:
prover-client:proving-agent:job-controller-363b3d7d Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.212]
INFO:
prover-client:proving-agent:job-controller-9601926d Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.216]
INFO:
prover-client:proving-agent:job-controller-269f3c6e Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.216]
WARN:
prover-client:proving-agent:job-controller-269f3c6e On complete handler error: Error: test error
{"jobId":"1"}
10:15:24 [10:15:24.218]
INFO:
prover-client:proving-agent:job-controller-2e7b696d Job controller started jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.219]
WARN:
prover-client:proving-agent:job-controller-2e7b696d Aborted job controller for jobId=1
{"jobId":"1"}
10:15:24 [10:15:24.222]
WARN:
prover-client:proving-agent:job-controller-2e7b696d Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:15:24
PASS src/proving_broker/proving_job_controller.test.ts
10:15:24 ProvingJobController
10:15:24
✓ reports IDLE status initially (7 ms)
10:15:24
✓ reports PROVING status while busy (16 ms)
10:15:24
✓ reports DONE status after job is done (19 ms)
10:15:24
✓ reports aborted error after cancellation (5 ms)
10:15:24
✓ calls onComplete (5 ms)
10:15:24
✓ calls onComplete with the error (3 ms)
10:15:24
✓ does not crash if onComplete throws (4 ms)
10:15:24
✓ calls onComplete if abort is called but result is masked (6 ms)
10:15:24
10:15:24
Test Suites: 1 passed, 1 total
10:15:24
Tests: 8 passed, 8 total
10:15:24
Snapshots: 0 total
10:15:24
Time: 4.235 s
10:15:24
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:15:24
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?