-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Mute InternalAutoDateHistogramTests.testReduceRandom #54542
Conversation
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 fails for 7.6 as well. Do we need backport? |
This'll fail for every branch for the past while. If it is a nuisance then we should. The failure seems to have started December 5th. I have no idea why it hasn't shown up until now. |
#45796 is where I bisected this failure to last night. |
Which enables the test. So it might go back further. I have no idea. |
Ok. You'll love this. It doesn't fail for me now. On any commit. that makes me think it is related to the current time. I'm going to start there! |
Ha!!!!!! |
@nik9000 I have no idea what the tests were doing. How does the current time affect the test results? Could you please elaborate a bit? Thanks |
Check it out! #54602
The short version is that the test data depended on the current time (in
epoch millis) and sometimes it'd hit the bug and sometimes not. The PR I
liked fixes it.
…On Wed, Apr 1, 2020, 20:36 Yang Wang ***@***.***> wrote:
@nik9000 <https://github.com/nik9000> I have no idea what the tests were
doing. How does the current time affect the test results? Could you please
elaborate a bit? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#54542 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABUXIWRTXGWOGFZQ4WRYHDRKPMZRANCNFSM4LYB6XDA>
.
|
Relates #54540
Relates #39497