Parent Log:
http://ci.aztec-labs.com/b428421cd9158c3f
Command: d57d38082bbaf86d yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/2d661b35c089f032f50de084b07dded86f0873b8
Env: REF_NAME=gh-readonly-queue/next/pr-15187-301dce04331dcfb583b7508b91491de618d4acf4 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 23 10:50:32 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15187_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
10:50:36 [10:50:36.744]
INFO:
prover-client:proving-agent:job-controller-c6e8efe0 Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.753]
INFO:
prover-client:proving-agent:job-controller-133884d9 Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.766]
INFO:
prover-client:proving-agent:job-controller-63ac718c Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.767]
WARN:
prover-client:proving-agent:job-controller-63ac718c Aborted job controller for jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.767]
WARN:
prover-client:proving-agent:job-controller-63ac718c Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:50:36 [10:50:36.774]
INFO:
prover-client:proving-agent:job-controller-a11339d1 Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.778]
INFO:
prover-client:proving-agent:job-controller-b34c0aab Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.783]
INFO:
prover-client:proving-agent:job-controller-3081cef8 Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.784]
WARN:
prover-client:proving-agent:job-controller-3081cef8 On complete handler error: Error: test error
{"jobId":"1"}
10:50:36 [10:50:36.787]
INFO:
prover-client:proving-agent:job-controller-3e4a289e Job controller started jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.788]
WARN:
prover-client:proving-agent:job-controller-3e4a289e Aborted job controller for jobId=1
{"jobId":"1"}
10:50:36 [10:50:36.792]
WARN:
prover-client:proving-agent:job-controller-3e4a289e Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:50:36
PASS src/proving_broker/proving_job_controller.test.ts
10:50:36 ProvingJobController
10:50:36
✓ reports IDLE status initially (5 ms)
10:50:36
✓ reports PROVING status while busy (11 ms)
10:50:36
✓ reports DONE status after job is done (12 ms)
10:50:36
✓ reports aborted error after cancellation (6 ms)
10:50:36
✓ calls onComplete (8 ms)
10:50:36
✓ calls onComplete with the error (3 ms)
10:50:36
✓ does not crash if onComplete throws (5 ms)
10:50:36
✓ calls onComplete if abort is called but result is masked (7 ms)
10:50:36
10:50:36
Test Suites: 1 passed, 1 total
10:50:36
Tests: 8 passed, 8 total
10:50:36
Snapshots: 0 total
10:50:36
Time: 3.257 s
10:50:36
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:50:36
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?