Parent Log:
http://ci.aztec-labs.com/24c394738399f7e2
Command: 246560b53abce7e6 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/69efc9daf98e823f486416900de52fe8a44f25d9
Env: REF_NAME=gh-readonly-queue/next/pr-15187-6e2f55a89973b55c8c3c210b7f3a692b4d3d6473 CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Mon Jun 23 16:12:41 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15187_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_34b66864f2808487_next
16:12:44
PASS src/public/avm/opcodes/storage.test.ts
16:12:44 Storage Instructions
16:12:44 SSTORE
16:12:44
✓ Should (de)serialize correctly (179 ms)
16:12:44
✓ Sstore should Write into storage (3 ms)
16:12:44
✓ Should not be able to write to storage in a static call (10 ms)
16:12:44
✓ Should charge da gas for cold storage (1 ms)
16:12:44
✓ Should not charge da gas when storage is hot (1 ms)
16:12:44 SLOAD
16:12:44
✓ Should (de)serialize correctly (3 ms)
16:12:44
✓ Sload should Read into storage (2 ms)
16:12:44
16:12:44
Test Suites: 1 passed, 1 total
16:12:44
Tests: 7 passed, 7 total
16:12:44
Snapshots: 0 total
16:12:44
Time: 1.395 s
16:12:44
Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts
.
16:12:44
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?