"Martin Dosch" <martin@mdosch.de> writes:
> Dear all,
>
> the current upload of go-crypto [1] is currently blocked dut to a
> ppc643l regression of golang-github-go-git-go-git [2], but actually the
> current upload of golang-github-go-git-go-git [3] is lacking a build on
> ppc64el as well due to the same issue [4].
>
> Is there anything I can do get go-crypto unblocked?
Do a team upload of golang-github-go-git-go-git making it build on
ppc64el and loong64.
Andrew, can you 'git push --all' and 'git push --tags' from your
golang-github-go-git-go-git checkout? It seems to be missing on Salsa.
Please try monitor packages you upload so they migrate to testing, or
reach out for help.
Why is the loong64 build log missing on the following page?!
https://buildd.debian.org/status/package.php?p=golang-github-go-git-go-git
The error seems to be:
=== RUN Test
----------------------------------------------------------------------
FAIL: common_test.go:111: CommonSuite.TestNewContextWriteCloser
common_test.go:123:
c.Assert(n, Equals, 0)
... obtained int = 1
... expected int = 0
OOPS: 8 passed, 1 FAILED
--- FAIL: Test (0.00s)
FAIL
FAIL github.com/go-git/go-git/utils/ioutil 0.007s
So some variation of something like
SKIP=TestNewContextWriteCloser
override_dh_auto_test:
dh_auto_test $(DH_BUILD_OPTS) -- -skip=$(SKIP)
-dh_auto_test $(DH_BUILD_OPTS) -- -run=$(SKIP)
may work. Try to investigate if this is a flaky or just failing test,
and report upstream so they are aware of this.
/Simon
> Best regards
> Martin
>
> [1] https://tracker.debian.org/pkg/golang-github-protonmail-go-crypto
> [2]
> https://ci.debian.net/packages/g/golang-github-go-git-go-git/testing/ppc64el/69607881/
> [3] https://tracker.debian.org/pkg/golang-github-go-git-go-git
> [4]
> https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-git-go-git&arch=ppc64el&ver=5.17.0-1&stamp=1773153859&raw=0
>
Attachment:
signature.asc
Description: PGP signature