time: TestLoadFixed failure

[ALTree]

What version of Go are you using (go version)?

$ gotip version
go version devel +847bc6d Thu Sep 29 10:56:03 2016 +0200 linux/amd64
$ uname -a
Linux [...] 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/[...]/gocode"
GORACE=""
GOROOT="/home/[...]/go"
GOTOOLDIR="/home/[...]/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build162033413=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?

$ cd src/time
$ gotip test -run=TestLoadFixed

What did you see?

--- FAIL: TestLoadFixed (0.00s)
    time_test.go:947: Now().In(loc).Zone() = "-01", -3600, want "GMT+1", -3600
FAIL
exit status 1
FAIL    time    0.003s

[ALTree]

A new version of tzdata, (tzdata-2016g), was released yesterday. From the changelog:

Several zones in Antarctica and the former Soviet Union, along
with zones intended for ships at sea that cannot use POSIX TZ
strings, now use numeric time zone abbreviations instead of
invented or obsolete alphanumeric abbreviations. The affected
zones are [...] Etc/GMT+1 [...]

Etc/GMT+1 is exactly the zone parsed in the failing test.

[ALTree]

Cooking up a patch.

[ALTree]

https://go-review.googlesource.com/#/c/29995

[lfam]

Applying the fix in c5434f2 to Go 1.4.3 (which can be used as a Go bootstrap compiler) does not work. It fails like this:

# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, linux/amd64.
lib9
go tool dist: missing file /tmp/guix-build-go-1.4.3.drv-0/go/include/fmt.h

Any advice?

[ianlancetaylor]

This issue is closed and the bug you are reporting is not related to it. Please ask on a forum instead; see https://golang.org/wiki/Questions . Thanks.

[banditsmile]

use go1.4.3 binary package on ubuntu16.04 to build go1.7.3 still face this time package failed problem

[ianlancetaylor]

@banditsmile This issue is closed. It is not expected to be fixed in 1.4.3 or 1.7.3. If you want to make a case to backport the change to an older release, please open a new issue. Thanks.