Parent Log:
http://ci.aztec-labs.com/8ca66f532d1b481c
Command: c6dc62f84205193f yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/3cbe7945c84145b8646cf5cf8fb730b915c0dc93
Env: REF_NAME=gh-readonly-queue/next/pr-15068-254faae7d330e160b14c6eaaa099dc92d4a9cac7 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 13:29:39 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15068_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
13:29:43 [13:29:43.946]
INFO:
prover-client:proving-agent:job-controller-7b54b974 Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.953]
INFO:
prover-client:proving-agent:job-controller-de2f4151 Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.978]
INFO:
prover-client:proving-agent:job-controller-4ad7d56e Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.979]
WARN:
prover-client:proving-agent:job-controller-4ad7d56e Aborted job controller for jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.979]
WARN:
prover-client:proving-agent:job-controller-4ad7d56e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:29:43 [13:29:43.983]
INFO:
prover-client:proving-agent:job-controller-5f2a5dbc Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.987]
INFO:
prover-client:proving-agent:job-controller-2a24602b Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.991]
INFO:
prover-client:proving-agent:job-controller-da82c666 Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.992]
WARN:
prover-client:proving-agent:job-controller-da82c666 On complete handler error: Error: test error
{"jobId":"1"}
13:29:43 [13:29:43.995]
INFO:
prover-client:proving-agent:job-controller-274b7d36 Job controller started jobId=1
{"jobId":"1"}
13:29:43 [13:29:43.996]
WARN:
prover-client:proving-agent:job-controller-274b7d36 Aborted job controller for jobId=1
{"jobId":"1"}
13:29:44 [13:29:44.003]
WARN:
prover-client:proving-agent:job-controller-274b7d36 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:29:44
PASS src/proving_broker/proving_job_controller.test.ts
13:29:44 ProvingJobController
13:29:44
✓ reports IDLE status initially (4 ms)
13:29:44
✓ reports PROVING status while busy (11 ms)
13:29:44
✓ reports DONE status after job is done (25 ms)
13:29:44
✓ reports aborted error after cancellation (4 ms)
13:29:44
✓ calls onComplete (4 ms)
13:29:44
✓ calls onComplete with the error (1 ms)
13:29:44
✓ does not crash if onComplete throws (5 ms)
13:29:44
✓ calls onComplete if abort is called but result is masked (11 ms)
13:29:44
13:29:44
Test Suites: 1 passed, 1 total
13:29:44
Tests: 8 passed, 8 total
13:29:44
Snapshots: 0 total
13:29:44
Time: 3.711 s
13:29:44
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
13:29:44
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?