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