-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cancun eth tests #1135
base: develop
Are you sure you want to change the base?
Cancun eth tests #1135
Conversation
… inside eth-tests; Call Carmens SelfDestruct6780;
# Conflicts: # ethtest/block_enviroment.go # executor/transaction_processor.go # go.mod # go.sum # txcontext/block_environment.go # txcontext/substate/block_environment.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a huge PR that would have benefited from being decomposed into multiple smaller PRs. For instance, the change of the GetDirectoryFiles
function now accepting a list of paths could be on its own. So could be the introduction of the chain configuration in the block environment.
Smaller, focused PRs pay off in improving the review process, and thus leading to better results in my experience.
Another observation is that for all those new features being added, very little unit tests are present covering those.
I can mostly provide feedback on coding style and a few additional observations. I think @wsodsong should make the final approval decision.
// GetChainConfig returns current setup for ChainConfig. | ||
GetChainConfig() *params.ChainConfig | ||
|
||
// GetRandom returns the random hash. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is "the" random hash? Just "a" random hash generated right at the spot or something more restricted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually dont know. The documentation is very limited but its used for creating Mixhash
in genesis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Random
is from Block context https://github.com/ethereum/go-ethereum/blob/8032b63f167938e6441d4be3eb49b12014d9bfc8/core/vm/evm.go#L67
I don't fully know how it works, but it has to do with mining diffuculty. It is not a random number.
# Conflicts: # ethtest/open.go # executor/rpc_request_provider.go # utils/directory.go
# Conflicts: # ethtest/block_enviroment.go # ethtest/open.go # ethtest/result.go # ethtest/state_test_context.go # ethtest/test_case_splitter.go # ethtest/test_case_splitter_test.go
// GetChainConfig returns current setup for ChainConfig. | ||
GetChainConfig() *params.ChainConfig | ||
|
||
// GetRandom returns the random hash. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Random
is from Block context https://github.com/ethereum/go-ethereum/blob/8032b63f167938e6441d4be3eb49b12014d9bfc8/core/vm/evm.go#L67
I don't fully know how it works, but it has to do with mining diffuculty. It is not a random number.
2cae2ea
to
e345a83
Compare
e3288ac
to
70deec1
Compare
Description
This PR adds creating
BlockContext
before transaction execution and allows passing dynamicChainConfig
to transaction execution.Both of these new features are necessary by
Cancun
tests insideeth-tests
.TODO:
Type of change