-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
initialize with new VoteState for tests #33518
Conversation
Codecov Report
@@ Coverage Diff @@
## master #33518 +/- ##
=======================================
Coverage 81.7% 81.7%
=======================================
Files 802 802
Lines 217872 217874 +2
=======================================
+ Hits 178144 178161 +17
+ Misses 39728 39713 -15 |
4fb744d
to
5889e02
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.
Totally onboard with de-tangling some of this code now that it is no longer necessary to include support for the oldest versions of these data structures.
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.
OMG yes thank you so much. This will eliminate a major source of flakiness in the web3.js tests.
Should this get backported to 1.17 at least? |
ah yeah good call |
(cherry picked from commit d4941cc)
Problem
Now that clusters are on 1.16 and the feature flag is set to be activated soon, it's fine to use the new vote state format for tests.
Summary of Changes
Update with new vote state format for tests. Should not affect any live functionality.
Fixes #33517