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