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