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