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