We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://ci.appveyor.com/project/osteele/tuesday:
go test ./... --- FAIL: TestStrftime (0.05s) Error Trace: strftime_test.go:134 Error: Not equal: expected: "Mon Jan 2 15:04:05 EST 2006" actual: "Mon Jan 2 15:04:05 2006" Messages: Strftime "%+" --- FAIL: TestStrftime_zones (0.00s) Error Trace: strftime_test.go:207 Error: Not equal: expected: "%z=-0500 %Z=EST" actual: "%z=+0000 %Z=EST" Messages: 02 Jan 06 15:04 EST --- FAIL: ExampleStrftime_timezone (0.00s) got: EDT +0000 +00:00 +00:00:00
The text was updated successfully, but these errors were encountered:
The issue was that setting the TZ environment variable has no effect on Windows.
The tests now pass if you set the timezone before running the tests, e.g. tzutil /s "Eastern Standard Time".
tzutil /s "Eastern Standard Time"
This fixes the appveyor, but is a gotcha for Windows development.
A fix is to remove the reliance on system timezone entirely, and update the tests to parse time strings in EST instead of local.
Sorry, something went wrong.
No branches or pull requests
See https://ci.appveyor.com/project/osteele/tuesday:
The text was updated successfully, but these errors were encountered: