-
Notifications
You must be signed in to change notification settings - Fork 152
Testing cleanups #191
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
Testing cleanups #191
Conversation
35d36d2 to
a9fb63b
Compare
|
Jenkins: test this please |
1 similar comment
|
Jenkins: test this please |
|
@dwightguth ready for review |
0c5aeb0 to
f78f5df
Compare
|
Jenkins: test mantis |
dwightguth
left a comment
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.
one thing that needs changing.
I also had one other question: are you intending to remove the VMTESTS mode in a future PR, or does that need to be done now?
| tests/ethereum-tests/VMTests/vmRandomTest/201503102037PYTHON.json \ | ||
| tests/ethereum-tests/VMTests/vmRandomTest/201503102148PYTHON.json \ | ||
| tests/ethereum-tests/VMTests/vmRandomTest/201503102300PYTHON.json \ | ||
| tests/ethereum-tests/VMTests/vmRandomTest/201503110050PYTHON.json \ |
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.
test-all-vm needs to not test the bad_vm_tests.
f78f5df to
bba1cbb
Compare
…mode, disable checking `callcreates` keys
|
@dwightguth I've excluded Once all the "bad" VMTests are removed (that is, all the VMTests which interact with network state at all), we should be able to completely remove VMTests mode. |
cleanups to testing harness extracted from #187 PR.