-
Notifications
You must be signed in to change notification settings - Fork 765
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
Refactor test runner #752
Refactor test runner #752
Conversation
f230b00
to
7039010
Compare
Codecov Report
@@ Coverage Diff @@
## master #752 +/- ##
==========================================
+ Coverage 91.63% 92.08% +0.44%
==========================================
Files 45 46 +1
Lines 2964 3006 +42
Branches 467 468 +1
==========================================
+ Hits 2716 2768 +52
+ Misses 150 144 -6
+ Partials 98 94 -4
Continue to review full report at Codecov.
|
958b34a
to
3b5f1fa
Compare
All green! |
Phew, did a lot of CI runs on this. I think I now have got it, will give a last ok once all the tests pass. I rolled back on promisification of util.setupPreconditions since this caused selected failures on all test types (API, StateTests, BlockchainTests) and I couldn't draw conclusions on the underlying root cause. So this can be tackled separately eventually. The last failed test runs of the blockchain tests were actually some previously hidden failure runs by passing on errors in places like here but never do anything with it. I have now fixed this, this was happening on a lot of test where there were |
d349085
to
b748290
Compare
…ests, code clean-up)
b748290
to
c441719
Compare
Ok, finally. All VM tests pass (I think the Block test failure can be safely ignored, this is just due to some GH Actions outage likely). So this is now ready for review. 😀 I added two additional tests to the skip list, these were exposed by the I also added two simple scripts for manually testing/triggering various CL options for testing the test runner a bit more systematically. |
Some more notes: The command executions from the two scripts pass apparently. The test exception declaration awareness is rather just a start than a final integration. At some point it might be worth to have a closer look again here if exceptions are actually thrown within an appropriate context and handled appropriately. Should nevertheless be some working ground for this round here. |
looking great 🎉 added a small commit to remove the |
@ryanio Thanks 😉, can you already give an approval or do you want to wait a bit longer? |
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.
lgtm!
Long overdue refactoring of the test runner. Sorry, this was such a mess and there was so much interdependent to correct that I gave up on keeping the changes separate and put everything in one commit. Hope this is somewhat reviewable. This should also proof to a greater extend correct if the CI runs pass, I will keep this in draft state for some more days and also do some more local failure case testing + testing of CL parameters and report back here.
PR does the following:
tests/config.js
VMTests
since not being used for years and being deprecated now for some time onethereum/tests
async
library usage (some missing inutil.js
)expectException[FORKNAME]
field in the test fileForkStressTest
blockchain test to skipped tests, should be addressed in a separate PR