Parent Log:
http://ci.aztec-labs.com/91d1f12a37080b18
Command: ebfed4061172f77e yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/07aee119a58dd438ddfb5bd53e124e7269e6c651
Env: REF_NAME=gh-readonly-queue/next/pr-15083-9b801754ba98479ee645488c29d2fda1eecbfd85 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 21:06:01 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15083_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
21:06:06 [21:06:06.496]
INFO:
prover-client:proving-agent:job-controller-6fcd98f4 Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.506]
INFO:
prover-client:proving-agent:job-controller-3218dc32 Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.534]
INFO:
prover-client:proving-agent:job-controller-1cd22aac Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.535]
WARN:
prover-client:proving-agent:job-controller-1cd22aac Aborted job controller for jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.536]
WARN:
prover-client:proving-agent:job-controller-1cd22aac Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
21:06:06 [21:06:06.540]
INFO:
prover-client:proving-agent:job-controller-9b3a593d Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.544]
INFO:
prover-client:proving-agent:job-controller-8c5dc56e Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.548]
INFO:
prover-client:proving-agent:job-controller-ba78e5af Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.549]
WARN:
prover-client:proving-agent:job-controller-ba78e5af On complete handler error: Error: test error
{"jobId":"1"}
21:06:06 [21:06:06.551]
INFO:
prover-client:proving-agent:job-controller-d0a6c97b Job controller started jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.552]
WARN:
prover-client:proving-agent:job-controller-d0a6c97b Aborted job controller for jobId=1
{"jobId":"1"}
21:06:06 [21:06:06.558]
WARN:
prover-client:proving-agent:job-controller-d0a6c97b Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
21:06:06
PASS src/proving_broker/proving_job_controller.test.ts
21:06:06 ProvingJobController
21:06:06
✓ reports IDLE status initially (4 ms)
21:06:06
✓ reports PROVING status while busy (9 ms)
21:06:06
✓ reports DONE status after job is done (29 ms)
21:06:06
✓ reports aborted error after cancellation (6 ms)
21:06:06
✓ calls onComplete (6 ms)
21:06:06
✓ calls onComplete with the error (2 ms)
21:06:06
✓ does not crash if onComplete throws (4 ms)
21:06:06
✓ calls onComplete if abort is called but result is masked (9 ms)
21:06:06
21:06:06
Test Suites: 1 passed, 1 total
21:06:06
Tests: 8 passed, 8 total
21:06:06
Snapshots: 0 total
21:06:06
Time: 3.754 s
21:06:06
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
21:06:06
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?