Parent Log: http://ci.aztec-labs.com/820a0bb63168d9da Command: b895a7fa8f839b60 yarn-project/scripts/run_test.sh stdlib/src/kernel/hints/build_note_hash_read_request_hints.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/408ec6f57f38faf5e1dbdf7712a82e2e1112be2c Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Sat Jun 14 11:24:45 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_46e1ed4f559d611f_next 11:24:47 PASS src/kernel/hints/build_note_hash_read_request_hints.test.ts 11:24:47 buildNoteHashReadRequestHints 11:24:47 ✓ builds empty hints (240 ms) 11:24:47 ✓ builds hints for pending note hash read requests (12 ms) 11:24:47 ✓ builds hints for settled note hash read requests (13 ms) 11:24:47 ✓ builds hints for mixed pending, settled and future note hash read requests (12 ms) 11:24:47 ✓ throws if cannot find a match in pending set and in the tree (11 ms) 11:24:47 11:24:47 Test Suites: 1 passed, 1 total 11:24:47 Tests: 5 passed, 5 total 11:24:47 Snapshots: 0 total 11:24:47 Time: 0.982 s 11:24:47 Ran all test suites matching /stdlib\/src\/kernel\/hints\/build_note_hash_read_request_hints.test.ts/i. 11:24:47 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?