You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior:
Test blockInfo from the VMTests suite fails for all tests, given that we currently hardcode most of the expected returned values (e.g. coinbase).
We could however have a few of them passing, such as block number but would need to update the runner in order to force Katana to jump to the correct block number and set the correct timestamp (and would need to do this for each test).
Expected behavior:
Post state should exist and test should pass using the post state.
make setup
make fetch-dump
make target=blockInfo ef-test
Failing output should be:
[!] Case /Users/greg/code/rust/ef-tests/crates/ef-testing/ethereum-tests/BlockchainTests/GeneralStateTests/VMTests/vmTests/blockInfo.json failed:
blockInfo_d0g0v0_Shanghai expected storage value 0x000000000000000000000000000000005018aa1fe0e6bc666dac8fc2697ff9ba for 0x0000000000000000000000000000000000000100, got 0x00000000000000000000000000000000acdffe0cf08e20ed8ba10ea97a487004
The text was updated successfully, but these errors were encountered:
Bug Report
Kakarot version: ee6458a
Current behavior:
Test
blockInfo
from theVMTests
suite fails for all tests, given that we currently hardcode most of the expected returned values (e.g. coinbase).We could however have a few of them passing, such as block number but would need to update the runner in order to force Katana to jump to the correct block number and set the correct timestamp (and would need to do this for each test).
Expected behavior:
Post state should exist and test should pass using the post state.
Steps to reproduce:
Failing output should be:
The text was updated successfully, but these errors were encountered: