From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: git@vger.kernel.org
Subject: Re: Testsuite failures on ppc64, sparc64 and s390x (64-bit BE)
Date: Sat, 4 Jan 2020 20:58:03 +0000 [thread overview]
Message-ID: <20200104205803.GE6570@camp.crustytoothpaste.net> (raw)
In-Reply-To: <34ed7497-643e-5a38-d68c-7c075b647bcd@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
On 2020-01-04 at 20:14:31, John Paul Adrian Glaubitz wrote:
> Hi!
>
> It seems that git is failing its testsuite on all 64-bit Big-Endian targets,
> full build log can be found in [1]. There seem to be multiple failures.
>
> The issue first showed with 2.25-rc1 [2].
This is interesting, because there are different failures on different
platforms. s390x shows failures only in t9100, which is one of the svn
tests. From the diff between rc0 and rc1, I don't see anything which
should affect git-svn in that way.
ppc64 and sparc64 failing a lot more tests, mostly due to segfaults, but
from a cursory glance they all appear to be SVN-related.
Are we sure that some dependency of libsvn1 hasn't caused this problem?
I noticed that all of the broken builds seem to have libserf-1-1
1.3.9-8, which appears to have received an overhaul recently. Of
course, it could be something else as well.
I got rid of my UltraSPARC hardware when I last moved, so I won't be
looking into this further, but it seems unlikely to me that the problem
is in Git when the only non-Windows C change between the two versions is
a one-line file name change.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2020-01-04 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 20:14 Testsuite failures on ppc64, sparc64 and s390x (64-bit BE) John Paul Adrian Glaubitz
2020-01-04 20:58 ` brian m. carlson [this message]
2020-01-04 21:07 ` John Paul Adrian Glaubitz
2020-01-06 23:31 ` Thomas Braun
2020-01-06 23:33 ` John Paul Adrian Glaubitz
2020-01-04 22:14 ` John Paul Adrian Glaubitz
2020-01-04 22:48 ` brian m. carlson
2020-01-04 23:13 ` John Paul Adrian Glaubitz
2020-02-09 0:58 ` John Paul Adrian Glaubitz
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=20200104205803.GE6570@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
/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).