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