-
Notifications
You must be signed in to change notification settings - Fork 440
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
Tests fail in a non-UTC timezone #757
Labels
Comments
archlinux-github
pushed a commit
to archlinux/svntogit-community
that referenced
this issue
Nov 11, 2020
- only change is test compat for pytest 6 - also set the timezone for the test, since it fails if you're not UTC: python-babel/babel#757 git-svn-id: file:///srv/repos/svn-community/svn@751201 9fca08f4-af9d-4005-b8df-a31f2cc04f65
archlinux-github
pushed a commit
to archlinux/svntogit-community
that referenced
this issue
Nov 11, 2020
- only change is test compat for pytest 6 - also set the timezone for the test, since it fails if you're not UTC: python-babel/babel#757 git-svn-id: file:///srv/repos/svn-community/svn@751201 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Fixed by #701. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It turns out that #747 is not the only problem running the testsuite. Trying to package the new 2.8.1 release, I discovered the tests passed on my remote build server, but failed on my laptop. I eventually pinned down the difference to the timezone in use. Exporting
TZ=UTC
before running the tests made it pass no matter which device I built on.Failure log (for git master) while using
TZ=EST
:The text was updated successfully, but these errors were encountered: