Parent Log:
http://ci.aztec-labs.com/8230d37b8e4008cc
Command: 03c0d59bf5b4a0b1 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/4b0e4dc09fa55f0bc808fa0c7c3e95e8fa997069
Env: REF_NAME=gh-readonly-queue/next/pr-15116-433ba6218aed45169029991a493e4232b30b8ec6 CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Tue Jun 17 20:30:04 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15116_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_46e1ed4f559d611f_next
20:30:05
PASS src/kernel/hints/build_note_hash_read_request_hints.test.ts
20:30:05 buildNoteHashReadRequestHints
20:30:05
✓ builds empty hints (177 ms)
20:30:05
✓ builds hints for pending note hash read requests (16 ms)
20:30:05
✓ builds hints for settled note hash read requests (15 ms)
20:30:05
✓ builds hints for mixed pending, settled and future note hash read requests (20 ms)
20:30:05
✓ throws if cannot find a match in pending set and in the tree (12 ms)
20:30:05
20:30:05
Test Suites: 1 passed, 1 total
20:30:05
Tests: 5 passed, 5 total
20:30:05
Snapshots: 0 total
20:30:05
Time: 0.735 s
20:30:05
Ran all test suites matching stdlib/src/kernel/hints/build_note_hash_read_request_hints.test.ts
.
20:30:05
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?