Parent Log:
http://ci.aztec-labs.com/4451244b7f022098
Command: 731d98bdb3377842 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/4110b08ca823c6af4399e58e54e0483d6e3459ed
Env: REF_NAME=gh-readonly-queue/next/pr-15064-daebab2c4bace59ef25ddb29040a040926f095e6 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 09:31:42 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15064_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
09:31:46 [09:31:46.154]
INFO:
prover-client:proving-agent:job-controller-d7a37d69 Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.164]
INFO:
prover-client:proving-agent:job-controller-4661c0f6 Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.172]
INFO:
prover-client:proving-agent:job-controller-a16ad125 Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.173]
WARN:
prover-client:proving-agent:job-controller-a16ad125 Aborted job controller for jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.174]
WARN:
prover-client:proving-agent:job-controller-a16ad125 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
09:31:46 [09:31:46.179]
INFO:
prover-client:proving-agent:job-controller-231e1675 Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.184]
INFO:
prover-client:proving-agent:job-controller-2248d55f Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.190]
INFO:
prover-client:proving-agent:job-controller-e598d16e Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.190]
WARN:
prover-client:proving-agent:job-controller-e598d16e On complete handler error: Error: test error
{"jobId":"1"}
09:31:46 [09:31:46.193]
INFO:
prover-client:proving-agent:job-controller-d33ef18d Job controller started jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.195]
WARN:
prover-client:proving-agent:job-controller-d33ef18d Aborted job controller for jobId=1
{"jobId":"1"}
09:31:46 [09:31:46.199]
WARN:
prover-client:proving-agent:job-controller-d33ef18d Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
09:31:46
PASS src/proving_broker/proving_job_controller.test.ts
09:31:46 ProvingJobController
09:31:46
✓ reports IDLE status initially (5 ms)
09:31:46
✓ reports PROVING status while busy (10 ms)
09:31:46
✓ reports DONE status after job is done (8 ms)
09:31:46
✓ reports aborted error after cancellation (5 ms)
09:31:46
✓ calls onComplete (6 ms)
09:31:46
✓ calls onComplete with the error (3 ms)
09:31:46
✓ does not crash if onComplete throws (5 ms)
09:31:46
✓ calls onComplete if abort is called but result is masked (9 ms)
09:31:46
09:31:46
Test Suites: 1 passed, 1 total
09:31:46
Tests: 8 passed, 8 total
09:31:46
Snapshots: 0 total
09:31:46
Time: 2.554 s
09:31:46
Ran all test suites matching /prover-client\/src\/proving_broker\/proving_job_controller.test.ts/i
.
09:31:46
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?