-
Notifications
You must be signed in to change notification settings - Fork 757
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
Add petersburg aka constantinopleFix support #433
Add petersburg aka constantinopleFix support #433
Conversation
2e63c71
to
e8f7d72
Compare
e858f81
to
fb81943
Compare
tests/GeneralStateTestsRunner.js
Outdated
@@ -126,7 +126,11 @@ function runTestCase (options, testData, t, cb) { | |||
|
|||
module.exports = function runStateTest (options, testData, t, cb) { | |||
try { | |||
const testCases = parseTestCases(options.forkConfig, testData, options.data, options.gasLimit, options.value) | |||
let aliasForkConfig | |||
if (options.forkConfig === 'Petersburg') { |
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.
Some note here: when I added the fork config logic here to the tests some time ago I added it in a way that both capital and non-capital names can be used, see e.g. here, so e.g.
Byzantiumor
byzantium`. Still not sure if this was a good idea, I actually already did a first take to remove this lately along some other PR and then stumbled over some unexpected stuff which made this a bit more complicated than expected.
So I would suggest also for now that we keep that behavior and concentrate on the Petersburg
changes. But to keep things consistent we should then also do these two Petersburg
comparisons in the PR case-agnostic and compare the lowercase versions.
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 have made changes in 948fcfa such that the fork config for tests can be provided 'petersburg' or 'Petersburg'.
However, I noticed that node ./tests/tester -s --fork="Byzantium"
works but node ./tests/tester -s --fork="byzantium" does not. This is because the ethereum/tests
assume that the fork names will be written in upper case. The 'petersburg'/'Petersburg' case is not affected because I've made the name check in the added hardfork alias logic case insensitive.
One way to address this would be the changes I pushed (with another branch) here: add-petersburg-aka-constantinople-fix-support...fix-test-fork-name-case-handling
fb81943
to
fe0d62d
Compare
e8f7d72
to
6451b75
Compare
7af05fe
to
020bc03
Compare
6451b75
to
da97a00
Compare
020bc03
to
948fcfa
Compare
da97a00
to
e6be3e1
Compare
948fcfa
to
1b31ead
Compare
…ltiple supported forks
0aa7bd8
to
ceb1787
Compare
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.
Looks good, thanks Dan for taking on this! 😄
Will directly prepare a release.
Addressses #423
constantinople
hardfork (and not on prior or subsequent hardforks).This is branched from #432
For this PR to work, we will also have to merge ethereumjs/ethereumjs-blockchain#86 and ethereumjs/ethereumjs-block#64, release new versions of those repos to npm and then update this PR to use those new versions.