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