Parent Log: http://ci.aztec-labs.com/6cc9fa695c7cfc03 Command: 4ef547fa5e299294 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/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=1 Date: Tue Jun 24 10:28:23 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15218_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_34b66864f2808487_next 10:28:26 PASS src/public/avm/opcodes/storage.test.ts 10:28:26 Storage Instructions 10:28:26 SSTORE 10:28:26 ✓ Should (de)serialize correctly (273 ms) 10:28:26 ✓ Sstore should Write into storage (5 ms) 10:28:26 ✓ Should not be able to write to storage in a static call (15 ms) 10:28:26 ✓ Should charge da gas for cold storage (3 ms) 10:28:26 ✓ Should not charge da gas when storage is hot (2 ms) 10:28:26 SLOAD 10:28:26 ✓ Should (de)serialize correctly (21 ms) 10:28:26 ✓ Sload should Read into storage (3 ms) 10:28:26 10:28:26 Test Suites: 1 passed, 1 total 10:28:26 Tests: 7 passed, 7 total 10:28:26 Snapshots: 0 total 10:28:26 Time: 1.873 s 10:28:26 Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts. 10:28:26 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?