Parent Log:
http://ci.aztec-labs.com/51fad2508877a18c
Command: 2f76ae4bba915073 yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_job_controller.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/87c4b689268afecc86ab007c3587e45110daa43d
Env: REF_NAME=gh-readonly-queue/next/pr-15220-282da3bd25d49b92970e6fc85f110092e8566299 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 24 16:34:58 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15220_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_4229e7da9f4a5d1e_next
16:35:02 [16:35:02.898]
INFO:
prover-client:proving-agent:job-controller-0abea4ad Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.906]
INFO:
prover-client:proving-agent:job-controller-c8d72686 Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.926]
INFO:
prover-client:proving-agent:job-controller-40501e28 Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.927]
WARN:
prover-client:proving-agent:job-controller-40501e28 Aborted job controller for jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.928]
WARN:
prover-client:proving-agent:job-controller-40501e28 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:35:02 [16:35:02.933]
INFO:
prover-client:proving-agent:job-controller-27ffa29b Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.937]
INFO:
prover-client:proving-agent:job-controller-74edf55e Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.946]
INFO:
prover-client:proving-agent:job-controller-41043537 Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.947]
WARN:
prover-client:proving-agent:job-controller-41043537 On complete handler error: Error: test error
{"jobId":"1"}
16:35:02 [16:35:02.950]
INFO:
prover-client:proving-agent:job-controller-10bf2289 Job controller started jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.952]
WARN:
prover-client:proving-agent:job-controller-10bf2289 Aborted job controller for jobId=1
{"jobId":"1"}
16:35:02 [16:35:02.957]
WARN:
prover-client:proving-agent:job-controller-10bf2289 Job controller for jobId=1 completed but job was aborted
{"currentStatus":"running","jobId":"1"}
16:35:02
PASS src/proving_broker/proving_job_controller.test.ts
16:35:02 ProvingJobController
16:35:02
✓ reports IDLE status initially (5 ms)
16:35:02
✓ reports PROVING status while busy (9 ms)
16:35:02
✓ reports DONE status after job is done (20 ms)
16:35:02
✓ reports aborted error after cancellation (7 ms)
16:35:02
✓ calls onComplete (6 ms)
16:35:02
✓ calls onComplete with the error (4 ms)
16:35:02
✓ does not crash if onComplete throws (7 ms)
16:35:02
✓ calls onComplete if abort is called but result is masked (9 ms)
16:35:02
16:35:02
Test Suites: 1 passed, 1 total
16:35:02
Tests: 8 passed, 8 total
16:35:02
Snapshots: 0 total
16:35:02
Time: 3.461 s
16:35:02
Ran all test suites matching prover-client/src/proving_broker/proving_job_controller.test.ts
.
16:35:02
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?