Source: golang-github-safchain-ethtool
Version: 0.4.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20250107 ftbfs-trixie

Hi,

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

This build was done using sbuild from bookworm-backports and the unshare
backend.

Relevant part (hopefully):
>  debian/rules binary
> dh binary --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 8 
> github.com/safchain/ethtool github.com/safchain/ethtool/example
> internal/unsafeheader
> internal/coverage/rtcov
> internal/goos
> internal/godebugs
> internal/goarch
> internal/goexperiment
> internal/byteorder
> internal/cpu
> internal/profilerecord
> internal/runtime/atomic
> internal/runtime/syscall
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> internal/race
> internal/chacha8rand
> sync/atomic
> unicode
> unicode/utf8
> internal/bytealg
> cmp
> internal/itoa
> math/bits
> internal/asan
> internal/msan
> encoding
> log/internal
> internal/runtime/exithook
> math
> internal/stringslite
> runtime
> iter
> internal/reflectlite
> sync
> slices
> internal/bisect
> internal/testlog
> errors
> sort
> internal/godebug
> io
> strconv
> internal/oserror
> path
> syscall
> bytes
> strings
> reflect
> internal/syscall/execenv
> internal/syscall/unix
> time
> io/fs
> internal/poll
> internal/filepathlite
> encoding/binary
> internal/fmtsort
> os
> golang.org/x/sys/unix
> fmt
> encoding/hex
> log
> flag
> github.com/safchain/ethtool
> github.com/safchain/ethtool/example
>    dh_auto_test -O--buildsystem=golang
>       cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/safchain/ethtool github.com/safchain/ethtool/example
> ?     github.com/safchain/ethtool/example     [no test files]
> === RUN   TestCmdGet
> testing on Debian.
> testing force success on Debian.
> --- PASS: TestCmdGet (0.00s)
> === RUN   TestCmdGetMapped
> testing on Debian.
> testing force success on Debian.
> --- PASS: TestCmdGetMapped (0.00s)
> === RUN   TestMsglvlGet
> testing on travis/Debian packaging.
> testing msglvl force success on travis or Debian packaging.
> --- PASS: TestMsglvlGet (0.00s)
> === RUN   TestGoString
> --- PASS: TestGoString (0.00s)
> === RUN   TestStats
>     ethtool_test.go:66: Unable to retrieve stats from any interface of this 
> system.
> --- FAIL: TestStats (0.00s)
> === RUN   TestDriverName
>     ethtool_test.go:86: Unable to retrieve driver from any interface of this 
> system.
> --- FAIL: TestDriverName (0.00s)
> === RUN   TestBusInfo
>     ethtool_test.go:106: Unable to retrieve bus info from any interface of 
> this system.
> --- FAIL: TestBusInfo (0.00s)
> === RUN   TestSupportedLinkModes
> --- PASS: TestSupportedLinkModes (0.00s)
> === RUN   TestFeatures
> --- PASS: TestFeatures (0.00s)
> FAIL
> FAIL  github.com/safchain/ethtool     0.006s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit 
> code 1


The full build log is available from:
http://qa-logs.debian.net/2025/01/07/golang-github-safchain-ethtool_0.4.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250107;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250107&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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 mark 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 mine
so that we can identify if something relevant changed in the meantime.

Reply via email to