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

Lucas Nussbaum lucas at debian.org
Sat Feb 13 17:12:16 GMT 2021


Source: golang-github-pkg-profile
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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/pkg/profile
> internal/unsafeheader
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> internal/race
> runtime/internal/math
> sync/atomic
> unicode
> internal/bytealg
> unicode/utf8
> internal/testlog
> math/bits
> math
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> strings
> bytes
> reflect
> hash
> bufio
> hash/crc32
> text/tabwriter
> internal/syscall/unix
> time
> internal/syscall/execenv
> context
> internal/poll
> encoding/binary
> internal/fmtsort
> os
> path/filepath
> os/signal
> fmt
> io/ioutil
> log
> runtime/trace
> compress/flate
> compress/gzip
> runtime/pprof
> github.com/pkg/profile
>    dh_auto_test -O--buildsystem=golang
> 	cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile
> # github.com/pkg/profile.test
> loadinternal: cannot find runtime/cgo
> === RUN   TestProfile
>     profile_test.go:200: default profile (cpu)
>     profile_test.go:220: stderr: wanted '[profile: cpu profiling enabled]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:35 profile: cpu profiling enabled, /tmp/profile867216648/cpu.pprof
>         2021/02/13 05:50:35 profile: cpu profiling disabled, /tmp/profile867216648/cpu.pprof
>         '
>     profile_test.go:200: memory profile
>     profile_test.go:220: stderr: wanted '[profile: memory profiling enabled]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:36 profile: memory profiling enabled (rate 4096), /tmp/profile525680101/mem.pprof
>         2021/02/13 05:50:36 profile: memory profiling disabled, /tmp/profile525680101/mem.pprof
>         '
>     profile_test.go:200: memory profile (rate 2048)
>     profile_test.go:220: stderr: wanted '[profile: memory profiling enabled (rate 2048)]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:36 profile: memory profiling enabled (rate 2048), /tmp/profile086753360/mem.pprof
>         2021/02/13 05:50:36 profile: memory profiling disabled, /tmp/profile086753360/mem.pprof
>         '
>     profile_test.go:200: double start
>     profile_test.go:220: stderr: wanted '[cpu profiling enabled profile: Start() already called]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:36 profile: cpu profiling enabled, /tmp/profile306850439/cpu.pprof
>         2021/02/13 05:50:36 profile: Start() already called
>         exit status 1
>         '
>     profile_test.go:200: block profile
>     profile_test.go:220: stderr: wanted '[profile: block profiling enabled]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:36 profile: block profiling enabled, /tmp/profile814120833/block.pprof
>         2021/02/13 05:50:37 profile: block profiling disabled, /tmp/profile814120833/block.pprof
>         '
>     profile_test.go:200: mutex profile
>     profile_test.go:220: stderr: wanted '[profile: mutex profiling enabled]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:37 profile: mutex profiling enabled, /tmp/profile626939674/mutex.pprof
>         2021/02/13 05:50:37 profile: mutex profiling disabled, /tmp/profile626939674/mutex.pprof
>         '
>     profile_test.go:200: profile path
>     profile_test.go:220: stderr: wanted '[profile: cpu profiling enabled, cpu.pprof]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:37 profile: cpu profiling enabled, cpu.pprof
>         2021/02/13 05:50:37 profile: cpu profiling disabled, cpu.pprof
>         '
>     profile_test.go:200: profile path error
>     profile_test.go:220: stderr: wanted '[could not create initial output]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:37 profile: could not create initial output directory: mkdir /tmp/profile_test023789093: not a directory
>         exit status 1
>         '
>     profile_test.go:200: multiple profile sessions
>     profile_test.go:220: stderr: wanted '[profile: cpu profiling enabled profile: cpu profiling disabled profile: memory profiling enabled profile: memory profiling disabled profile: block profiling enabled profile: block profiling disabled profile: cpu profiling enabled profile: cpu profiling disabled profile: mutex profiling enabled profile: mutex profiling disabled]', got '# command-line-arguments
>         loadinternal: cannot find runtime/cgo
>         2021/02/13 05:50:38 profile: cpu profiling enabled, /tmp/profile707842275/cpu.pprof
>         2021/02/13 05:50:38 profile: cpu profiling disabled, /tmp/profile707842275/cpu.pprof
>         2021/02/13 05:50:38 profile: memory profiling enabled (rate 4096), /tmp/profile812756710/mem.pprof
>         2021/02/13 05:50:38 profile: memory profiling disabled, /tmp/profile812756710/mem.pprof
>         2021/02/13 05:50:38 profile: block profiling enabled, /tmp/profile976920333/block.pprof
>         2021/02/13 05:50:38 profile: block profiling disabled, /tmp/profile976920333/block.pprof
>         2021/02/13 05:50:38 profile: cpu profiling enabled, /tmp/profile561721608/cpu.pprof
>         2021/02/13 05:50:38 profile: cpu profiling disabled, /tmp/profile561721608/cpu.pprof
>         2021/02/13 05:50:38 profile: mutex profiling enabled, /tmp/profile012523719/mutex.pprof
>         2021/02/13 05:50:38 profile: mutex profiling disabled, /tmp/profile012523719/mutex.pprof
>         '
>     profile_test.go:200: profile quiet
>     profile_test.go:228: stderr: wanted 0 bytes, got 63
> --- FAIL: TestProfile (3.62s)
> === RUN   TestValidateOutput
> --- PASS: TestValidateOutput (0.00s)
> FAIL
> FAIL	github.com/pkg/profile	3.624s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2021/02/13/golang-github-pkg-profile_1.2.1-2_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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.



More information about the Pkg-go-maintainers mailing list