git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 22:48:30 +0000	[thread overview]
Message-ID: <20200104224830.GF6570@camp.crustytoothpaste.net> (raw)
In-Reply-To: <b7565f06-55a2-7087-d46e-94f9e7ada988@physik.fu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]

On 2020-01-04 at 22:14:21, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> On 1/4/20 9:14 PM, John Paul Adrian Glaubitz wrote:
> > 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.
> 
> Just checked out git with git from github (SCNR ;)) and built and ran the
> testsuite on ppc64, s390x and sparc64.
> 
> ppc64:
> 
> make aggregate-results
> make[3]: Entering directory '/srv/glaubitz/git-git/t'
> for f in 'test-results'/t*-*.counts; do \
>         echo "$f"; \
> done | '/bin/sh' ./aggregate-results.sh
> fixed   0
> success 20683
> failed  0
> broken  239
> total   21161
> 
> s390x:
> 
> make aggregate-results
> make[3]: Entering directory '/home/glaubitz/git/t'
> for f in 'test-results'/t*-*.counts; do \
>         echo "$f"; \
> done | '/bin/sh' ./aggregate-results.sh
> fixed   0
> success 21298
> failed  0
> broken  249
> total   21760
> 
> sparc64:
> 
> make aggregate-results
> make[3]: Entering directory '/home/glaubitz/git/t'
> for f in 'test-results'/t*-*.counts; do \
>         echo "$f"; \
> done | '/bin/sh' ./aggregate-results.sh
> fixed   0
> success 20703
> failed  0
> broken  239
> total   21176
> 
> So, it looks like the failures might be specific to the Debian package,
> doesn't it? Where there maybe any recent commits that may have fixed
> those issues?

Did you build your version of Git with Subversion support, and if so,
which version of Subversion did you use (version of Debian package or
other source)?  The tests that were failing all require git-svn, which
in turn require libsvn-perl and subversion (/usr/bin/svn).  If you're
missing those packages, the Subversion tests will automatically be
skipped.

The latest version on master is 2.25-rc1, and that's failing in the
Debian package.  I haven't checked recently, but last I looked, the
Debian package wasn't applying any additional patches on top of Git, so
the version you're getting off GitHub is literally the same version that
you're getting in the Debian package.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

  reply	other threads:[~2020-01-04 22:48 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
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 [this message]
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=20200104224830.GF6570@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).