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