Parent Log: http://ci.aztec-labs.com/7fc79c48d0a2fc40 Command: 448a16f463e450de 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/80d800435dd8dfa325e38593d83b405488449dba Env: REF_NAME=gh-readonly-queue/next/pr-14444-28bf32bfc2566751e8baa0a9125a9db20d474bee CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 15:59:10 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14444_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_46e1ed4f559d611f_next 15:59:11 PASS src/kernel/hints/build_note_hash_read_request_hints.test.ts 15:59:11 buildNoteHashReadRequestHints 15:59:11 builds empty hints (204 ms) 15:59:11 builds hints for pending note hash read requests (23 ms) 15:59:11 builds hints for settled note hash read requests (30 ms) 15:59:11 builds hints for mixed pending, settled and future note hash read requests (23 ms) 15:59:11 throws if cannot find a match in pending set and in the tree (16 ms) 15:59:11 15:59:11 Test Suites: 1 passed, 1 total 15:59:11 Tests: 5 passed, 5 total 15:59:11 Snapshots: 0 total 15:59:11 Time: 0.911 s 15:59:11 Ran all test suites matching stdlib/src/kernel/hints/build_note_hash_read_request_hints.test.ts. 15:59:11 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?