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