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