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