Parent Log: http://ci.aztec-labs.com/6502c8659d040e3d Command: 7ad4152ecf607d72 yarn-project/scripts/run_test.sh simulator/src/public/state_manager/state_manager.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/57cc88b8fb35fd431b9aa5cc1f99ec4e59f66a15 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Wed Jun 11 23:41:22 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_6f6fb72348c6c7fe_next 23:41:24 PASS src/public/state_manager/state_manager.test.ts 23:41:24 state_manager 23:41:24 Public Storage 23:41:24 When reading from storage, should check the cache first, and be appended to read/write journal (207 ms) 23:41:24 UTXOs & messages 23:41:24 checkNoteHashExists works for missing note hashes (2 ms) 23:41:24 checkNoteHashExists works for existing note hashes (1 ms) 23:41:24 writeNoteHash works (6 ms) 23:41:24 checkNullifierExists works for missing nullifiers (2 ms) 23:41:24 checkNullifierExists works for existing nullifiers (1 ms) 23:41:24 writeNullifier works (2 ms) 23:41:24 checkL1ToL2MessageExists works for missing message (1 ms) 23:41:24 checkL1ToL2MessageExists works for existing message (1 ms) 23:41:24 Should maintain l1 messages (1 ms) 23:41:24 Getting contract instances 23:41:24 Should get contract instance (3 ms) 23:41:24 Can get undefined contract instance 23:41:24 Getting bytecode 23:41:24 Should get bytecode (4 ms) 23:41:24 Can get undefined bytecode 23:41:24 23:41:24 Test Suites: 1 passed, 1 total 23:41:24 Tests: 14 passed, 14 total 23:41:24 Snapshots: 0 total 23:41:24 Time: 1.358 s 23:41:24 Ran all test suites matching /simulator\/src\/public\/state_manager\/state_manager.test.ts/i. 23:41:24 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?