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