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