Parent Log: http://ci.aztec-labs.com/963630247fdd03f4 Command: 69b6d6ef87c6fae3 yarn-project/scripts/run_test.sh simulator/src/public/state_manager/public_storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d4893155ff105399557b55c16450c39921c70d11 Env: REF_NAME=gh-readonly-queue/next/pr-15218-7edf16da6c056f9499e2dfd9c71fb9b7580f9bfc CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 24 10:30:46 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15218_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_e771954551aaa34c_next 10:30:47 PASS src/public/state_manager/public_storage.test.ts 10:30:47 avm public storage 10:30:47 Should be able to merge two public storages together (1 ms) 10:30:47 AVM Public Storage 10:30:47 Reading an unwritten slot works (gets zero & DNE) (4 ms) 10:30:47 Should cache storage write, reading works after write (1 ms) 10:30:47 Reading works on fallback to host (gets value & exists) (1 ms) 10:30:47 Reading works on fallback to parent (gets value & exists) (1 ms) 10:30:47 Reading works on fallback to grandparent (gets value & exists) (1 ms) 10:30:47 When reading from storage, should check cache, then parent, then host (1 ms) 10:30:47 10:30:47 Test Suites: 1 passed, 1 total 10:30:47 Tests: 7 passed, 7 total 10:30:47 Snapshots: 0 total 10:30:47 Time: 0.472 s 10:30:47 Ran all test suites matching simulator/src/public/state_manager/public_storage.test.ts. 10:30:47 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?