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