Parent Log:
http://ci.aztec-labs.com/68d1f31de3dea9be
Command: a8cc061dbe484831 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/58696523cc93fda453138a4f2c2dff72b21f0bfa
Env: REF_NAME=gh-readonly-queue/next/pr-15180-a923b0dd4c74291fcefa86c41b3b5dffca7e4178 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 13:10:17 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15180_amd64_x4-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
13:10:22 [13:10:22.648]
INFO:
prover-client:proving-agent:job-controller-a4485e01 Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.656]
INFO:
prover-client:proving-agent:job-controller-72e2c29d Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.673]
INFO:
prover-client:proving-agent:job-controller-2399a347 Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.674]
WARN:
prover-client:proving-agent:job-controller-2399a347 Aborted job controller for jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.675]
WARN:
prover-client:proving-agent:job-controller-2399a347 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:10:22 [13:10:22.680]
INFO:
prover-client:proving-agent:job-controller-b30f79de Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.689]
INFO:
prover-client:proving-agent:job-controller-65af00fc Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.699]
INFO:
prover-client:proving-agent:job-controller-bd7c3c6b Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.699]
WARN:
prover-client:proving-agent:job-controller-bd7c3c6b On complete handler error: Error: test error
{"jobId":"1"}
13:10:22 [13:10:22.702]
INFO:
prover-client:proving-agent:job-controller-7b7f4281 Job controller started jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.704]
WARN:
prover-client:proving-agent:job-controller-7b7f4281 Aborted job controller for jobId=1
{"jobId":"1"}
13:10:22 [13:10:22.710]
WARN:
prover-client:proving-agent:job-controller-7b7f4281 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
13:10:22
PASS src/proving_broker/proving_job_controller.test.ts
13:10:22 ProvingJobController
13:10:22
✓ reports IDLE status initially (6 ms)
13:10:22
✓ reports PROVING status while busy (11 ms)
13:10:22
✓ reports DONE status after job is done (18 ms)
13:10:22
✓ reports aborted error after cancellation (5 ms)
13:10:22
✓ calls onComplete (8 ms)
13:10:22
✓ calls onComplete with the error (7 ms)
13:10:22
✓ does not crash if onComplete throws (8 ms)
13:10:22
✓ calls onComplete if abort is called but result is masked (10 ms)
13:10:22
13:10:22
Test Suites: 1 passed, 1 total
13:10:22
Tests: 8 passed, 8 total
13:10:22
Snapshots: 0 total
13:10:22
Time: 3.779 s
13:10:22
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
13:10:22
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?