-
Notifications
You must be signed in to change notification settings - Fork 89
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
Fix time analyzer tests #1677
Comments
@monocle Oh nice. Can you change your date to Mar 2 (or even like Mar 10 just to be safe) and see if they all pass? |
It looks like they will.
…On Wed, Mar 1, 2023 at 7:55 AM Kent Shikama ***@***.***> wrote:
@monocle <https://github.com/monocle> Oh nice. Can you change your date
to Mar 2 and see if they all pass?
—
Reply to this email directly, view it on GitHub
<#1677 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4WPTAXM3UVGD7IWGT3MFF3WZ5WNVANCNFSM6AAAAAAVMHHYSQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sweet! |
Aha, the leap day bug strikes again! #899 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prior to Feb 28, 2023, the
test_time_analyzer
suit was passing. On Feb 28, 2023, four test failed:On Mar 1, 2023, only one test fails:
Manually changing local computer time can reproduce the problems.
The text was updated successfully, but these errors were encountered: