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