Parent Log:
http://ci.aztec-labs.com/b7b32e7ba238914c
Command: ca4daf70a894f3c3 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/f00eacfba6ea2df3bf79b8555d747c7a0ad38241
Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0
Date: Fri Jun 20 16:54:57 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
16:55:01 [16:55:01.214]
INFO:
prover-client:proving-agent:job-controller-223d1deb Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.222]
INFO:
prover-client:proving-agent:job-controller-0b3cd221 Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.258]
INFO:
prover-client:proving-agent:job-controller-2c2c9968 Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.259]
WARN:
prover-client:proving-agent:job-controller-2c2c9968 Aborted job controller for jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.259]
WARN:
prover-client:proving-agent:job-controller-2c2c9968 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:55:01 [16:55:01.264]
INFO:
prover-client:proving-agent:job-controller-a3ff3c9f Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.268]
INFO:
prover-client:proving-agent:job-controller-8444e6ee Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.273]
INFO:
prover-client:proving-agent:job-controller-0fa2cb65 Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.274]
WARN:
prover-client:proving-agent:job-controller-0fa2cb65 On complete handler error: Error: test error
{"jobId":"1"}
16:55:01 [16:55:01.276]
INFO:
prover-client:proving-agent:job-controller-bbd518aa Job controller started jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.278]
WARN:
prover-client:proving-agent:job-controller-bbd518aa Aborted job controller for jobId=1
{"jobId":"1"}
16:55:01 [16:55:01.282]
WARN:
prover-client:proving-agent:job-controller-bbd518aa Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:55:01
PASS src/proving_broker/proving_job_controller.test.ts
16:55:01 ProvingJobController
16:55:01
✓ reports IDLE status initially (4 ms)
16:55:01
✓ reports PROVING status while busy (8 ms)
16:55:01
✓ reports DONE status after job is done (37 ms)
16:55:01
✓ reports aborted error after cancellation (5 ms)
16:55:01
✓ calls onComplete (6 ms)
16:55:01
✓ calls onComplete with the error (3 ms)
16:55:01
✓ does not crash if onComplete throws (5 ms)
16:55:01
✓ calls onComplete if abort is called but result is masked (8 ms)
16:55:01
16:55:01
Test Suites: 1 passed, 1 total
16:55:01
Tests: 8 passed, 8 total
16:55:01
Snapshots: 0 total
16:55:01
Time: 3.202 s
16:55:01
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
16:55:01
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?