Parent Log:
http://ci.aztec-labs.com/70098e3969a404f8
Command: 4d0fb449c606d482 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/263498dd65e8700218979d7a94dbfd25b2a8a8a8
Env: REF_NAME=gh-readonly-queue/next/pr-14921-4b0e4dc09fa55f0bc808fa0c7c3e95e8fa997069 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 20:35:43 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14921_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
20:35:47 [20:35:47.421]
INFO:
prover-client:proving-agent:job-controller-bbf2ea11 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.428]
INFO:
prover-client:proving-agent:job-controller-0d291e90 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.450]
INFO:
prover-client:proving-agent:job-controller-7491d7b0 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.451]
WARN:
prover-client:proving-agent:job-controller-7491d7b0 Aborted job controller for jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.451]
WARN:
prover-client:proving-agent:job-controller-7491d7b0 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:35:47 [20:35:47.458]
INFO:
prover-client:proving-agent:job-controller-c9caa311 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.463]
INFO:
prover-client:proving-agent:job-controller-6a4351e2 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.468]
INFO:
prover-client:proving-agent:job-controller-4a243d99 Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.468]
WARN:
prover-client:proving-agent:job-controller-4a243d99 On complete handler error: Error: test error
{"jobId":"1"}
20:35:47 [20:35:47.471]
INFO:
prover-client:proving-agent:job-controller-414dd0ca Job controller started jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.473]
WARN:
prover-client:proving-agent:job-controller-414dd0ca Aborted job controller for jobId=1
{"jobId":"1"}
20:35:47 [20:35:47.477]
WARN:
prover-client:proving-agent:job-controller-414dd0ca Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
20:35:47
PASS src/proving_broker/proving_job_controller.test.ts
20:35:47 ProvingJobController
20:35:47
✓ reports IDLE status initially (5 ms)
20:35:47
✓ reports PROVING status while busy (9 ms)
20:35:47
✓ reports DONE status after job is done (21 ms)
20:35:47
✓ reports aborted error after cancellation (6 ms)
20:35:47
✓ calls onComplete (7 ms)
20:35:47
✓ calls onComplete with the error (2 ms)
20:35:47
✓ does not crash if onComplete throws (6 ms)
20:35:47
✓ calls onComplete if abort is called but result is masked (8 ms)
20:35:47
20:35:47
Test Suites: 1 passed, 1 total
20:35:47
Tests: 8 passed, 8 total
20:35:47
Snapshots: 0 total
20:35:47
Time: 3.256 s
20:35:47
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
20:35:47
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?