Parent Log: http://ci.aztec-labs.com/ce57deeae491c23c Command: a5bf9fa49c3b3b54 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/8cc8a56892d36191eefb49254ebbe49ea99ef4b8 Env: REF_NAME=gh-readonly-queue/next/pr-14921-78d87cb88633aee537d022d6fd8e57ceb74a3a95 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Wed Jun 18 11:37:56 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14921_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_34b66864f2808487_next 11:37:58 PASS src/public/avm/opcodes/storage.test.ts 11:37:58 Storage Instructions 11:37:58 SSTORE 11:37:58 ✓ Should (de)serialize correctly (194 ms) 11:37:58 ✓ Sstore should Write into storage (4 ms) 11:37:58 ✓ Should not be able to write to storage in a static call (10 ms) 11:37:58 ✓ Should charge da gas for cold storage (2 ms) 11:37:58 ✓ Should not charge da gas when storage is hot (2 ms) 11:37:58 SLOAD 11:37:58 ✓ Should (de)serialize correctly (1 ms) 11:37:58 ✓ Sload should Read into storage (1 ms) 11:37:58 11:37:58 Test Suites: 1 passed, 1 total 11:37:58 Tests: 7 passed, 7 total 11:37:58 Snapshots: 0 total 11:37:58 Time: 1.362 s 11:37:58 Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts. 11:37:58 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?