Fix InternalAutoDateHistogramTests (backport of #54602) #54688
Merged
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.
The test had errors around time units that have different length - think
leap years or months that aren't 30 days. This fixes those errors. In
the proces I've changed a bunch of things to debug the problem:
currentTimeMillis
with a random time. Now the test failsrandomly! Wonderful. Much better than on random days of the month.
this we were super frequently getting stuck in the "year of century"
rounding because some of the of the buckets we built were far apart.
This generates a much greater variety of tests.
toString
onRoundingInfo
so I can debug without goingcrazy.
Instant
sso we can read the failures.
Closes #54540
Closes #39497