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