Parent Log: http://ci.aztec-labs.com/c148bc90788ce605 Command: 069d70048f6bf27e 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/08d3f55874836a573c4756b0cc7279160b0813a3 Env: REF_NAME=gh-readonly-queue/next/pr-15167-aac426c9418162aeee8162ed45014b9393d605b8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 10:06:07 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15167_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_46e1ed4f559d611f_next 10:06:09 PASS src/kernel/hints/build_note_hash_read_request_hints.test.ts 10:06:09 buildNoteHashReadRequestHints 10:06:09 builds empty hints (249 ms) 10:06:09 builds hints for pending note hash read requests (19 ms) 10:06:09 builds hints for settled note hash read requests (29 ms) 10:06:09 builds hints for mixed pending, settled and future note hash read requests (18 ms) 10:06:09 throws if cannot find a match in pending set and in the tree (10 ms) 10:06:09 10:06:09 Test Suites: 1 passed, 1 total 10:06:09 Tests: 5 passed, 5 total 10:06:09 Snapshots: 0 total 10:06:09 Time: 0.95 s 10:06:09 Ran all test suites matching stdlib/src/kernel/hints/build_note_hash_read_request_hints.test.ts. 10:06:09 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?