Parent Log:
http://ci.aztec-labs.com/4fd3ef431e05f779
Command: 0f4f65dca0a2798e yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/storage.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/67bf12030291ce3da2cf39ff5fbfa799eae98dc5
Env: REF_NAME=gh-readonly-queue/next/pr-14963-42440bd429a3b283b3a344db0be4652d818bd261 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 20:02:15 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14963_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:02:18
PASS src/public/avm/opcodes/storage.test.ts
20:02:18 Storage Instructions
20:02:18 SSTORE
20:02:18
✓ Should (de)serialize correctly (282 ms)
20:02:18
✓ Sstore should Write into storage (5 ms)
20:02:18
✓ Should not be able to write to storage in a static call (14 ms)
20:02:18
✓ Should charge da gas for cold storage (3 ms)
20:02:18
✓ Should not charge da gas when storage is hot (2 ms)
20:02:18 SLOAD
20:02:18
✓ Should (de)serialize correctly (1 ms)
20:02:18
✓ Sload should Read into storage (2 ms)
20:02:18
20:02:18
Test Suites: 1 passed, 1 total
20:02:18
Tests: 7 passed, 7 total
20:02:18
Snapshots: 0 total
20:02:18
Time: 1.945 s
20:02:18
Ran all test suites matching simulator/src/public/avm/opcodes/storage.test.ts
.
20:02:18
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?