[pkg-go] Bug#952199: golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit code 1

[Lucas Nussbaum]

Source: golang-github-boltdb-bolt
Version: 1.3.1-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_test -- -short
> 	cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt
> flag provided but not defined: -test.testlogfile
> Usage of /tmp/go-build232881692/b001/bolt.test:
>   -quick.count int
>     	 (default 5)
>   -quick.maxitems int
>     	 (default 1000)
>   -quick.maxksize int
>     	 (default 1024)
>   -quick.maxvsize int
>     	 (default 1024)
>   -quick.seed int
>     	 (default 4109)
>   -quickchecks int
>     	The default number of iterations for each check (default 100)
>   -stats
>     	show performance stats
> FAIL	github.com/boltdb/bolt	0.002s
> === RUN   TestInfoCommand_Run
> --- PASS: TestInfoCommand_Run (0.00s)
> === RUN   TestStatsCommand_Run_EmptyDatabase
> --- PASS: TestStatsCommand_Run_EmptyDatabase (0.00s)
> === RUN   TestStatsCommand_Run
> --- PASS: TestStatsCommand_Run (0.01s)
> === RUN   TestCompactCommand_Run
> --- PASS: TestCompactCommand_Run (0.30s)
> PASS
> ok  	github.com/boltdb/bolt/cmd/bolt	0.318s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/golang-github-boltdb-bolt_1.3.1-6_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.