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