Timezone tests fail on Windows
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with strftime_test.go at the failures reported on lines 134 and 207, and run go test ./... in a Windows environment. Check the timezone-related expectations and ExampleStrftime_timezone output; done when these tests pass on Windows with the expected EST/EDT and offset values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100