Allow quick e2e test reruns #9028
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Developers could previously avoid rerunning most of the setup for e2e tests by commenting out the
hooks.before()call. #6471 broke this by adding a new value on geth instances that was set only athooks.beforetime, but not athooks.restarttime. With this PR, the necessary values are set inhooks.restart, allowing for e2e test reruns without having to wait for migrations and other initialization steps after having run them once.Tested
Before, after running the governance e2e tests once, commenting out the
hooks.before()call, and running the e2e tests again, the tests would fail with "Error: miner.validator address from the instance is required". With these changes, e2e tests run as expected.