[pkg-go] Bug#835685: golint: FTBFS: dh_auto_test: go test -v -p 1 github.com/golang/lint github.com/golang/lint/golint returned exit code 1

[Lucas Nussbaum]

Source: golint
Version: 0.0+git20150623.7b7f436-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160828 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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>    dh_testdir -O--buildsystem=golang
>    dh_update_autotools_config -O--buildsystem=golang
>    dh_auto_configure -O--buildsystem=golang
>    dh_auto_build -O--buildsystem=golang
> 	go install -v -p 1 github.com/golang/lint github.com/golang/lint/golint
> golang.org/x/tools/go/exact
> golang.org/x/tools/go/types
> golang.org/x/tools/go/gcimporter
> github.com/golang/lint
> github.com/golang/lint/golint
>    dh_auto_test -O--buildsystem=golang
> 	go test -v -p 1 github.com/golang/lint github.com/golang/lint/golint
> === RUN   TestAll
> --- FAIL: TestAll (0.01s)
> 	lint_test.go:95: Lint failed at errorf.go:29; /should replace.*t\.Error\(fmt\.Sprintf\(\.\.\.\)\).*t\.Errorf\(\.\.\.\)/ did not match
> 	lint_test.go:95: Lint failed at time.go:11; /Msec.*\*time.Duration/ did not match
> 	lint_test.go:95: Lint failed at time.go:13; /Secs.*time.Duration/ did not match
> === RUN   TestLine
> --- PASS: TestLine (0.00s)
> === RUN   TestLintName
> --- PASS: TestLintName (0.00s)
> === RUN   TestExportedType
> --- PASS: TestExportedType (0.00s)
> FAIL
> exit status 1
> FAIL	github.com/golang/lint	0.015s
> ?   	github.com/golang/lint/golint	[no test files]
> dh_auto_test: go test -v -p 1 github.com/golang/lint github.com/golang/lint/golint returned exit code 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/golint_0.0+git20150623.7b7f436-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.