On Mon, 06 Oct 2025 09:38:32 +0200, Simon Josefsson <simon@josefsson.org> wrote: > Testing migration for golang-go.crypto is here: > > https://tracker.debian.org/pkg/golang-go.crypto > > It looks fairly fine, but will probably take some time until everything > is aligned. I think this is a good opportunity to catch and report (and > fix) flaky tests in our Go packages, I've encountered a couple alredy. > > There is one autopkgtest failure for golang-go.crypto itself that I > don't understand. Does anyone knows why this happens? Only on s390x. > > I've rescheduled this in case it is flaky, but the error suggests it is > not. > > https://ci.debian.net/packages/g/golang-go.crypto/testing/s390x/64965225/ There’s an s390x-specific implementation, <https://cs.opensource.google/go/x/crypto/+/master:sha3/sha3_s390x.go>, but it doesn’t implement MarshalBinary (added in <https://go-review.googlesource.com/c/crypto/+/616635>). See also <https://github.com/golang/go/issues/73681>. Regards, Stephen
Attachment:
pgpXPggXbz4Q_.pgp
Description: OpenPGP digital signature