Parent Log:
http://ci.aztec-labs.com/05b76684a53e6d24
Command: 0d541f5a731ac42b yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/74eeec5d95106217d3b3f3068853022cef7fa307
Env: REF_NAME=gh-readonly-queue/next/pr-15189-8cbdad5ba8c6b2b13d060ecb764f4818ca0d5e4d CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 25 10:26:05 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15189_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:26:10 [10:26:10.472]
INFO:
prover-client:proving-agent:job-controller-976f9377 Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.479]
INFO:
prover-client:proving-agent:job-controller-6cc39f4a Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.493]
INFO:
prover-client:proving-agent:job-controller-ac77e674 Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.494]
WARN:
prover-client:proving-agent:job-controller-ac77e674 Aborted job controller for jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.494]
WARN:
prover-client:proving-agent:job-controller-ac77e674 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:26:10 [10:26:10.500]
INFO:
prover-client:proving-agent:job-controller-709dd9b7 Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.505]
INFO:
prover-client:proving-agent:job-controller-08106b9d Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.511]
INFO:
prover-client:proving-agent:job-controller-4bfa0de6 Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.512]
WARN:
prover-client:proving-agent:job-controller-4bfa0de6 On complete handler error: Error: test error
{"jobId":"1"}
10:26:10 [10:26:10.524]
INFO:
prover-client:proving-agent:job-controller-37882171 Job controller started jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.526]
WARN:
prover-client:proving-agent:job-controller-37882171 Aborted job controller for jobId=1
{"jobId":"1"}
10:26:10 [10:26:10.531]
WARN:
prover-client:proving-agent:job-controller-37882171 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
10:26:10
PASS src/proving_broker/proving_job_controller.test.ts
10:26:10 ProvingJobController
10:26:10
✓ reports IDLE status initially (4 ms)
10:26:10
✓ reports PROVING status while busy (8 ms)
10:26:10
✓ reports DONE status after job is done (14 ms)
10:26:10
✓ reports aborted error after cancellation (4 ms)
10:26:10
✓ calls onComplete (7 ms)
10:26:10
✓ calls onComplete with the error (3 ms)
10:26:10
✓ does not crash if onComplete throws (15 ms)
10:26:10
✓ calls onComplete if abort is called but result is masked (9 ms)
10:26:10
10:26:10
Test Suites: 1 passed, 1 total
10:26:10
Tests: 8 passed, 8 total
10:26:10
Snapshots: 0 total
10:26:10
Time: 3.796 s
10:26:10
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
10:26:10
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?