Parent Log: http://ci.aztec-labs.com/fd1e4573060c2f4f Command: 03ab2c8f0cfe2a95 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/77a00686be4080a71b03d68671da6c8b270b62aa Env: REF_NAME=gh-readonly-queue/next/pr-14961-fa23733be8278348dff0959c8094bcfd89eb44d5 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 12 10:50:32 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14961_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:50:34 PASS src/public/avm/opcodes/storage.test.ts 10:50:34 Storage Instructions 10:50:34 SSTORE 10:50:34 Should (de)serialize correctly (246 ms) 10:50:34 Sstore should Write into storage (5 ms) 10:50:34 Should not be able to write to storage in a static call (13 ms) 10:50:34 Should charge da gas for cold storage (2 ms) 10:50:34 Should not charge da gas when storage is hot (1 ms) 10:50:34 SLOAD 10:50:34 Should (de)serialize correctly (1 ms) 10:50:34 Sload should Read into storage (1 ms) 10:50:34 10:50:34 Test Suites: 1 passed, 1 total 10:50:34 Tests: 7 passed, 7 total 10:50:34 Snapshots: 0 total 10:50:34 Time: 1.779 s 10:50:34 Ran all test suites matching /simulator\/src\/public\/avm\/opcodes\/storage.test.ts/i. 10:50:34 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?