Parent Log: http://ci.aztec-labs.com/4b713613dbcdc560 Command: 5d6e163c4654d5d0 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/ada03190841b1923625905b0e6ea3bdc4a3b3e84 Env: REF_NAME=gh-readonly-queue/next/pr-14953-1650b3d017a2a4fa5182c8787e79cc108e24e1f4 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 10:53:02 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14953_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_34b66864f2808487_next 10:53:04 PASS src/public/avm/opcodes/storage.test.ts 10:53:04 Storage Instructions 10:53:04 SSTORE 10:53:04 Should (de)serialize correctly (186 ms) 10:53:04 Sstore should Write into storage (3 ms) 10:53:04 Should not be able to write to storage in a static call (10 ms) 10:53:04 Should charge da gas for cold storage (1 ms) 10:53:04 Should not charge da gas when storage is hot (2 ms) 10:53:04 SLOAD 10:53:04 Should (de)serialize correctly (1 ms) 10:53:04 Sload should Read into storage (1 ms) 10:53:04 10:53:04 Test Suites: 1 passed, 1 total 10:53:04 Tests: 7 passed, 7 total 10:53:04 Snapshots: 0 total 10:53:04 Time: 1.223 s 10:53:04 Ran all test suites matching /simulator\/src\/public\/avm\/opcodes\/storage.test.ts/i. 10:53:04 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?