[pkg-go] Bug#839474: golang-github-gorilla-handlers: FTBFS: Tests failures

[Lucas Nussbaum]

Source: golang-github-gorilla-handlers
Version: 1.1-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> panic(0x68d920, 0xc4205a00a0)
> 	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1
> testing.tRunner.func1(0xc42001cfc0)
> 	/usr/lib/go-1.7/src/testing/testing.go:579 +0x25d
> panic(0x68d920, 0xc4205a00a0)
> 	/usr/lib/go-1.7/src/runtime/panic.go:458 +0x243
> github.com/gorilla/handlers.TestWriteLog(0xc42001cfc0)
> 	/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/gorilla/handlers/handlers_test.go:79 +0xe79
> testing.tRunner(0xc42001cfc0, 0x709310)
> 	/usr/lib/go-1.7/src/testing/testing.go:610 +0x81
> created by testing.(*T).Run
> 	/usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec
> exit status 2
> FAIL	github.com/gorilla/handlers	0.011s
> dh_auto_test: go test -v -p 1 -short github.com/gorilla/handlers returned exit code 1
> debian/rules:4: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/golang-github-gorilla-handlers_1.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.