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/
162s --- FAIL: TestMarshalUnmarshal (0.00s)
162s --- FAIL: TestMarshalUnmarshal/SHA3-224 (0.00s)
162s panic: interface conversion: *sha3.asmState is not encoding.BinaryMarshaler: missing method MarshalBinary [recovered]
162s panic: interface conversion: *sha3.asmState is not encoding.BinaryMarshaler: missing method MarshalBinary
162s
162s goroutine 33 [running]:
162s testing.tRunner.func1.2({0x1ddb00, 0xc0000a2f30})
162s /usr/lib/go-1.24/src/testing/testing.go:1734 +0x2b4
162s testing.tRunner.func1()
162s /usr/lib/go-1.24/src/testing/testing.go:1737 +0x3d6
162s panic({0x1ddb00, 0xc0000a2f30})
162s /usr/lib/go-1.24/src/runtime/panic.go:792 +0x11a
162s golang.org/x/crypto/sha3.testMarshalUnmarshal(0xc0004ff880, {0x24c8b0, 0xc0000c8d88})
162s /tmp/autopkgtest-lxc.nozj3tgj/downtmp/autopkgtest_tmp/_build/src/golang.org/x/crypto/sha3/sha3_test.go:512 +0x1b4
162s golang.org/x/crypto/sha3.TestMarshalUnmarshal.func1(0xc0004ff880)
162s /tmp/autopkgtest-lxc.nozj3tgj/downtmp/autopkgtest_tmp/_build/src/golang.org/x/crypto/sha3/sha3_test.go:491 +0x42
162s testing.tRunner(0xc0004ff880, 0x217a30)
162s /usr/lib/go-1.24/src/testing/testing.go:1792 +0x132
162s created by testing.(*T).Run in goroutine 32
162s /usr/lib/go-1.24/src/testing/testing.go:1851 +0x4e4
162s FAIL golang.org/x/crypto/sha3 4.783s
/Simon
Attachment:
signature.asc
Description: PGP signature