time: Failing test: TestParseInSydney in Go 1.3.2 #8814
Labels
Milestone
Comments
Same failed test here.
Version:
go version go1.3.2 linux/amd64
Steps to reproduce:
cd /usr/local/go
sudo hg pull
sudo hg update release # per Andrew's instructions
cd src
sudo ./all.bash
What happened:
--- FAIL: TestParseInSydney (0.00 seconds)
format_test.go:201: ParseInLocation(Feb 01 2013 EST, Sydney) = 2013-02-01 00:00:00 +0000 EST, want 2013-02-01 00:00:00 +1100 AEDT
FAIL
FAIL time 2.416s
Additional info:
OS: Debian Testing w/latest as of 9/25.
Running in a VirtualBox VM on OSX, configured for "Hardware clock in UTC time" Which
states, "If checked, VirtualBox will report the system time in UTC format to the guest
instead of local (host) time. This affects how the virtual real-time clock (RTC)
operates and may be useful for Unix-like guest operating systems, which typically expect
the hardware clock to be set to UTC."
As mentioned by the reporter, I also removed the installation and pulled a fresh copy -
no modifications.
But, I continue to have the build error.
Andrew mentioned in the google thread that its a timezone issue:
https://groups.google.com/d/msg/golang-nuts/eeOHNw_shwU/hpoUb4OKUdEJ
As I mentioned above, I am passing UTC bios clock to my VM, but the Debian install is
set to EDT:
spdev01:/usr/local$ date
Fri Sep 26 08:21:44 EDT 2014
Thanks!
|
This is issue #8547. The fix is https://golang.org/cl/130920043. Status changed to Duplicate. Merged into issue #8547. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What does 'go version' print? go version go1.3.2 darwin/amd64 What steps reproduce the problem? 1. hg pull && hg update 2. cd src 3. ./all.bash What happened? --- FAIL: TestParseInSydney (0.00 seconds) format_test.go:201: ParseInLocation(Feb 01 2013 EST, Sydney) = 2013-02-01 00:00:00 +0000 EST, want 2013-02-01 00:00:00 +1100 AEDT Please provide any additional information below. I have Mac OS X Mavericks 10.9.5. I removed the original installation and tried to build on a fresh clone but I got the same result.The text was updated successfully, but these errors were encountered: