#976924 golang-github-hashicorp-raft: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/hashicorp/raft github.com/hashicorp/raft/bench returned exit code 1

#976924#5
Date:
2020-12-09 09:03:52 UTC
From:
To:
Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package has only
Architecture:all binary packages, and should thus, in theory, build
everywhere. Failure to build on ppc64el might indicate a serious issue
in this package or in another package.

But feel free to downgrade or close if you believe that this is only a
build-time issue. (I would personnally prefer a severity:minor bug just to
track that the package can only be built on specific architectures.)

Relevant part (hopefully):
http://qa-logs.debian.net/2020/12/09/golang-github-hashicorp-raft_1.1.2-1_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 a Power8 cluster part of the
Grid'5000 testbed. Hardware specs: https://www.grid5000.fr/w/Grenoble:Hardware#drac

#976924#10
Date:
2020-12-23 16:16:55 UTC
From:
To:
Looking at the logs, it really looks like timeouts in the testsuite. We could disable the tests on problematic architectures, patches welcome. As a workaround, I'd suggest building the package with export DEB_BUILD_OPTIONS=notest. With this, I'm downgrading the severity to normal to avoid having dozens of packages removed from testing.