Source: golang-go-xdg
Version: 0~bzr20140219-1
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20160707 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 launchpad.net/go-xdg/v0
> launchpad.net/go-xdg/v0
>    dh_auto_test -O--buildsystem=golang
>       go test -v launchpad.net/go-xdg/v0
> === RUN   TestXDGd
> 
> ----------------------------------------------------------------------
> FAIL: <autogenerated>:5: xdgdNoHomeSuite.TestDirsUsesDefault
> 
> base_directory_test.go:71:
>     c.Check(hs[0], Matches, s.home+".*"+s.val1)
> ... value string = "/home/user/something"
> ... regex string = "/sbuild-nonexistent.*something"
> 
> 
> ----------------------------------------------------------------------
> FAIL: <autogenerated>:2: xdgdNoHomeSuite.TestHomeUsesDefault
> 
> base_directory_test.go:45:
>     c.Check(h, Matches, s.home+".*"+s.val1)
> ... value string = "/home/user/something"
> ... regex string = "/sbuild-nonexistent.*something"
> 
> OOPS: 16 passed, 2 FAILED
> --- FAIL: TestXDGd (0.00s)
> FAIL
> exit status 1
> FAIL  launchpad.net/go-xdg/v0 0.007s
> dh_auto_test: go test -v launchpad.net/go-xdg/v0 returned exit code 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/golang-go-xdg_0~bzr20140219-1_unstable_reb.normal.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.

Reply via email to