Parent Log:
http://ci.aztec-labs.com/f9daaf627a43018f
Command: 53eb328a1446f762 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/a48851a8c6884f4b9615a154f8862a549722d25e
Env: REF_NAME=gh-readonly-queue/next/pr-14680-3b5835195491b53670250790b18c14d922718574 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 11:29:12 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14680_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
11:29:17 [11:29:17.599]
INFO:
prover-client:proving-agent:job-controller-2d67d882 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.606]
INFO:
prover-client:proving-agent:job-controller-959afbc4 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.623]
INFO:
prover-client:proving-agent:job-controller-3ec51606 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.624]
WARN:
prover-client:proving-agent:job-controller-3ec51606 Aborted job controller for jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.624]
WARN:
prover-client:proving-agent:job-controller-3ec51606 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:29:17 [11:29:17.629]
INFO:
prover-client:proving-agent:job-controller-2de4d3a0 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.632]
INFO:
prover-client:proving-agent:job-controller-74fbcd09 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.638]
INFO:
prover-client:proving-agent:job-controller-4174dbaa Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.639]
WARN:
prover-client:proving-agent:job-controller-4174dbaa On complete handler error: Error: test error
{"jobId":"1"}
11:29:17 [11:29:17.641]
INFO:
prover-client:proving-agent:job-controller-748a4e08 Job controller started jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.643]
WARN:
prover-client:proving-agent:job-controller-748a4e08 Aborted job controller for jobId=1
{"jobId":"1"}
11:29:17 [11:29:17.647]
WARN:
prover-client:proving-agent:job-controller-748a4e08 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
11:29:17
PASS src/proving_broker/proving_job_controller.test.ts
11:29:17 ProvingJobController
11:29:17
✓ reports IDLE status initially (5 ms)
11:29:17
✓ reports PROVING status while busy (9 ms)
11:29:17
✓ reports DONE status after job is done (16 ms)
11:29:17
✓ reports aborted error after cancellation (6 ms)
11:29:17
✓ calls onComplete (5 ms)
11:29:17
✓ calls onComplete with the error (3 ms)
11:29:17
✓ does not crash if onComplete throws (5 ms)
11:29:17
✓ calls onComplete if abort is called but result is masked (7 ms)
11:29:17
11:29:17
Test Suites: 1 passed, 1 total
11:29:17
Tests: 8 passed, 8 total
11:29:17
Snapshots: 0 total
11:29:17
Time: 3.931 s
11:29:17
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
11:29:17
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?