Hi Simon, thanks for the followup.
On Wed, Apr 25, 2012 at 02:54:15PM +0200, Simon Josefsson wrote: > Philipp Kern <pk...@debian.org> writes: > > your package FTBFSes on s390x because of a crash / failures in the > > testsuite: > > > > make[3]: Leaving directory > > /build/buildd-shishi_1.0.1-1-s390x-luumdM/shishi-1.0.1/tests' > > /usr/bin/make check-TESTS > > make[3]: Entering directory > > /build/buildd-shishi_1.0.1-1-s390x-luumdM/shishi-1.0.1/tests' > > shishi_authenticator_seqnumber_get() failed > > shishi_authenticator_seqnumber_get() failed > > shishi_authenticator_client() failed > > shishi_authenticator_client() failed > > shishi_authenticator_clientrealm() failed > > shishi_authenticator_authorizationdata() failed > > shishi_authenticator_cusec_get() failed > > shishi_authenticator_ctime() failed > > FAIL: authenticator > > Hi. Thanks for the report. I would either need a shell account on this > architecture, or your help in tracking this down. Could you get a gdb > backtrace of the self-test that crashes? Do you have any ideas on what > makes this architecture different from all the others, where it builds > and passes self-tests fine? Does it use the same gcc/glibc/linux > versions as other build hosts? It's 64bit big endian, which isn't the case for all other Debian architectures (except debian-ports ppc64 and sparc64). As a DM you can request guest access yourself by following [1], you don't need anybody to vouch for you or something. If you don't want to do that I can go and collect a backtrace, but it might take a few days, too. Kind regards Philipp Kern [1] http://dsa.debian.org/doc/guest-account/
signature.asc
Description: Digital signature