Parent Log: http://ci.aztec-labs.com/cb895239f73ec9af Command: b3bf99625f6f0a17 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d5a262aabc20f5384a720a0d831e2ec28badc7f9 Env: REF_NAME=gh-readonly-queue/next/pr-15042-17ea18ade041a1bb437806e047c30b29da124094 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 18:06:04 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_34b66864f2808487_next 18:06:07 PASS src/public/avm/opcodes/storage.test.ts 18:06:07 Storage Instructions 18:06:07 SSTORE 18:06:07 ✓ Should (de)serialize correctly (250 ms) 18:06:07 ✓ Sstore should Write into storage (5 ms) 18:06:07 ✓ Should not be able to write to storage in a static call (19 ms) 18:06:07 ✓ Should charge da gas for cold storage (18 ms) 18:06:07 ✓ Should not charge da gas when storage is hot (4 ms) 18:06:07 SLOAD 18:06:07 ✓ Should (de)serialize correctly (2 ms) 18:06:07 ✓ Sload should Read into storage (2 ms) 18:06:07 18:06:07 Test Suites: 1 passed, 1 total 18:06:07 Tests: 7 passed, 7 total 18:06:07 Snapshots: 0 total 18:06:07 Time: 1.872 s 18:06:07 Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts. 18:06:07 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?