Parent Log:
http://ci.aztec-labs.com/15d7aef1c9d1b5f2
Command: b54d5ade67e7ffc9 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/347f29fb98cc855ead57129b4d1a444d9fb16820
Env: REF_NAME=gh-readonly-queue/next/pr-15059-16fc84676c7308fa5f7ca4a54b67319803d0f5b7 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 16:01:20 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15059_amd64_x4-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
16:01:24 [16:01:24.423]
INFO:
prover-client:proving-agent:job-controller-955a4764 Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.436]
INFO:
prover-client:proving-agent:job-controller-749ec76b Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.476]
INFO:
prover-client:proving-agent:job-controller-168fa130 Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.477]
WARN:
prover-client:proving-agent:job-controller-168fa130 Aborted job controller for jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.477]
WARN:
prover-client:proving-agent:job-controller-168fa130 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:01:24 [16:01:24.481]
INFO:
prover-client:proving-agent:job-controller-2a572b04 Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.485]
INFO:
prover-client:proving-agent:job-controller-10ef2550 Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.489]
INFO:
prover-client:proving-agent:job-controller-f0cf2cfc Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.489]
WARN:
prover-client:proving-agent:job-controller-f0cf2cfc On complete handler error: Error: test error
{"jobId":"1"}
16:01:24 [16:01:24.492]
INFO:
prover-client:proving-agent:job-controller-0d7208f0 Job controller started jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.493]
WARN:
prover-client:proving-agent:job-controller-0d7208f0 Aborted job controller for jobId=1
{"jobId":"1"}
16:01:24 [16:01:24.499]
WARN:
prover-client:proving-agent:job-controller-0d7208f0 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:01:24
PASS src/proving_broker/proving_job_controller.test.ts
16:01:24 ProvingJobController
16:01:24
✓ reports IDLE status initially (6 ms)
16:01:24
✓ reports PROVING status while busy (16 ms)
16:01:24
✓ reports DONE status after job is done (42 ms)
16:01:24
✓ reports aborted error after cancellation (4 ms)
16:01:24
✓ calls onComplete (5 ms)
16:01:24
✓ calls onComplete with the error (3 ms)
16:01:24
✓ does not crash if onComplete throws (3 ms)
16:01:24
✓ calls onComplete if abort is called but result is masked (9 ms)
16:01:24
16:01:24
Test Suites: 1 passed, 1 total
16:01:24
Tests: 8 passed, 8 total
16:01:24
Snapshots: 0 total
16:01:24
Time: 2.814 s
16:01:24
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
16:01:24
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?