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