Parent Log: http://ci.aztec-labs.com/f58a71454a9abef7 Command: 68e9475192d7aeac yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f495236d35f9bb0d1086b7ec79256c2c2b7c98b8 Env: REF_NAME=gh-readonly-queue/staging/pr-15201-f0619dd82429a5973f3e1da8d7eb0877264908e3 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Sat Jun 21 13:20:33 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15201_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_34b66864f2808487_staging 13:20:35 PASS src/public/avm/opcodes/storage.test.ts 13:20:35 Storage Instructions 13:20:35 SSTORE 13:20:35 ✓ Should (de)serialize correctly (231 ms) 13:20:35 ✓ Sstore should Write into storage (3 ms) 13:20:35 ✓ Should not be able to write to storage in a static call (10 ms) 13:20:35 ✓ Should charge da gas for cold storage (1 ms) 13:20:35 ✓ Should not charge da gas when storage is hot (1 ms) 13:20:35 SLOAD 13:20:35 ✓ Should (de)serialize correctly (1 ms) 13:20:35 ✓ Sload should Read into storage (2 ms) 13:20:35 13:20:35 Test Suites: 1 passed, 1 total 13:20:35 Tests: 7 passed, 7 total 13:20:35 Snapshots: 0 total 13:20:35 Time: 1.56 s 13:20:35 Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts. 13:20:35 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?