Source: golang-github-go-errors-errors Version: 1.0.1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye
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_update_autotools_config -O--buildsystem=golang > dh_autoreconf -O--buildsystem=golang > dh_auto_configure -O--buildsystem=golang > dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/go-errors/errors > internal/race > internal/cpu > runtime/internal/sys > runtime/internal/atomic > sync/atomic > runtime/internal/math > unicode > unicode/utf8 > math/bits > internal/bytealg > internal/testlog > math > runtime > internal/reflectlite > sync > errors > sort > io > strconv > internal/oserror > syscall > bytes > strings > reflect > time > internal/syscall/unix > internal/poll > internal/fmtsort > os > path/filepath > fmt > io/ioutil > github.com/go-errors/errors > dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 > github.com/go-errors/errors > === RUN TestStackFormat > TestStackFormat: error_test.go:26: Stack didn't match > TestStackFormat: error_test.go:27: First entry PC diff to large (-41) > Actual stack trace: > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:21 > (0x5030b0) > github.com/go-errors/errors.TestStackFormat.func1 > /usr/lib/go-1.14/src/runtime/panic.go:967 (0x431ef5) > runtime.gopanic > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:245 > (0x500bf3) > github.com/go-errors/errors.c > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:241 > (0x500bd7) > github.com/go-errors/errors.b > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:236 > (0x500bd6) > github.com/go-errors/errors.a > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:42 > (0x500bd5) > github.com/go-errors/errors.TestStackFormat > /usr/lib/go-1.14/src/testing/testing.go:992 (0x4c373b) > testing.tRunner > /usr/lib/go-1.14/src/runtime/asm_amd64.s:1373 (0x4622c0) > runtime.goexit > > Expected stack trace: > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:21 > (0x503087) > github.com/go-errors/errors.TestStackFormat.func1 > /usr/lib/go-1.14/src/runtime/panic.go:967 (0x431ef5) > runtime.gopanic > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:245 > (0x500bf3) > github.com/go-errors/errors.c > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:241 > (0x500bd7) > github.com/go-errors/errors.b > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:236 > (0x500bd6) > github.com/go-errors/errors.a > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:42 > (0x500bd5) > github.com/go-errors/errors.TestStackFormat > /usr/lib/go-1.14/src/testing/testing.go:992 (0x4c373b) > testing.tRunner > /usr/lib/go-1.14/src/runtime/asm_amd64.s:1373 (0x4622c0) > runtime.goexit > --- FAIL: TestStackFormat (0.00s) > === RUN TestSkipWorks > --- PASS: TestSkipWorks (0.00s) > === RUN TestNew > --- PASS: TestNew (0.00s) > === RUN TestIs > --- PASS: TestIs (0.00s) > === RUN TestWrapError > --- PASS: TestWrapError (0.00s) > === RUN TestWrapPrefixError > --- PASS: TestWrapPrefixError (0.00s) > === RUN TestParsePanic > --- PASS: TestParsePanic (0.00s) > FAIL > FAIL github.com/go-errors/errors 0.003s > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 > github.com/go-errors/errors returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2020/03/21/golang-github-go-errors-errors_1.0.1-3_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.
