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