From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: git@vger.kernel.org
Subject: [BUG]: Testsuite failures on big-endian targets
Date: Wed, 31 Jul 2019 08:37:13 +0200 [thread overview]
Message-ID: <b0bec82e-ad0a-32f6-e2e6-e1f0e6920639@physik.fu-berlin.de> (raw)
Hello!
Recent versions of git are failing the testsuite on big-endian targets
such as s390x in Debian.
Build logs are:
> https://buildd.debian.org/status/fetch.php?pkg=git&arch=s390x&ver=1%3A2.23.0%7Erc0-1&stamp=1564449102&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=git&arch=s390x&ver=1%3A2.23.0%7Erc0%2Bnext.20190729-1&stamp=1564449397&raw=0
Unfortunately, I cannot really read from the build logs which test in
particular is actually failing as I see a lot of lines starting with
the string "error".
Access to big-endian machines such as sparc64 can be retrieved through
the gcc compile farm [1].
Thanks,
Adrian
> [1] https://gcc.gnu.org/wiki/CompileFarm
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2019-07-31 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:37 John Paul Adrian Glaubitz [this message]
2019-07-31 7:17 ` [BUG]: Testsuite failures on big-endian targets Todd Zullinger
2019-10-19 21:38 ` John Paul Adrian Glaubitz
2019-10-19 23:37 ` [PATCH] test-progress: fix test failures on big-endian systems SZEDER Gábor
2019-10-19 23:55 ` John Paul Adrian Glaubitz
2019-10-20 0:19 ` Todd Zullinger
2019-10-21 0:52 ` Junio C Hamano
2019-10-21 3:21 ` Jeff King
2019-10-21 8:51 ` Junio C Hamano
2019-10-21 18:49 ` Jeff King
2019-10-23 1:58 ` Junio C Hamano
2019-10-24 17:24 ` SZEDER Gábor
2019-10-24 17:55 ` Jeff King
2019-10-20 0:26 ` [BUG]: Testsuite failures on big-endian targets Todd Zullinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0bec82e-ad0a-32f6-e2e6-e1f0e6920639@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).