Parent Log: http://ci.aztec-labs.com/43b01264fa252894 Command: f1d5df06d37e0c0f yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/5c77169d7f01a9e15bc19b05fa231fd96111d7dd Env: REF_NAME=gh-readonly-queue/next/pr-15042-d5c48d855d83e19712c6b72281801c6fce176ec1 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 15:02:12 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_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:02:15 PASS src/public/avm/opcodes/storage.test.ts 15:02:15 Storage Instructions 15:02:15 SSTORE 15:02:15 ✓ Should (de)serialize correctly (256 ms) 15:02:15 ✓ Sstore should Write into storage (5 ms) 15:02:15 ✓ Should not be able to write to storage in a static call (15 ms) 15:02:15 ✓ Should charge da gas for cold storage (2 ms) 15:02:15 ✓ Should not charge da gas when storage is hot (2 ms) 15:02:15 SLOAD 15:02:15 ✓ Should (de)serialize correctly (3 ms) 15:02:15 ✓ Sload should Read into storage (14 ms) 15:02:15 15:02:15 Test Suites: 1 passed, 1 total 15:02:15 Tests: 7 passed, 7 total 15:02:15 Snapshots: 0 total 15:02:15 Time: 1.866 s 15:02:15 Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts. 15:02:15 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?