-
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
reduce WARN logging to only necessary scenario #33408
Conversation
Codecov Report
@@ Coverage Diff @@
## master #33408 +/- ##
=======================================
Coverage 81.9% 81.9%
=======================================
Files 798 798
Lines 216974 216974
=======================================
+ Hits 177902 177905 +3
+ Misses 39072 39069 -3 |
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.
This looks okay to me, but I don't have the complete context from the original changeset. It might be a good idea to have one of your reviewers from that PR approve this.
Please backport to v1.16 to prevent spamming the (soon to be) stable TestValidator with these warnings.
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
(cherry picked from commit cc4e928)
(cherry picked from commit cc4e928)
…3408) (#33444) reduce WARN logging to only necessary scenario (#33408) (cherry picked from commit cc4e928) Co-authored-by: Tao Zhu <[email protected]>
…3408) (#33445) reduce WARN logging to only necessary scenario (#33408) (cherry picked from commit cc4e928) Co-authored-by: Tao Zhu <[email protected]>
Problem
A WARN log being excessively triggered by vote-only slots. It was meant to log an unlikely event when duplicated bank had prioritized TXs but the confirmed bank had none. It is not entirely impossible, but maybe something worth looking into, hence logging.
Summary of Changes
Fixes #