From: Todd Zullinger <tmz@pobox.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] test-progress: fix test failures on big-endian systems
Date: Sat, 19 Oct 2019 20:19:59 -0400 [thread overview]
Message-ID: <20191020001959.GY10893@pobox.com> (raw)
In-Reply-To: <f0d216a8-95ee-bdec-4116-012906117aad@physik.fu-berlin.de>
Hi,
John Paul Adrian Glaubitz wrote:
> Hi Gábor!
>
> On 10/20/19 1:37 AM, SZEDER Gábor wrote:
>> On Sat, Oct 19, 2019 at 11:38:40PM +0200, John Paul Adrian Glaubitz wrote:
>>> The testsuite is failing again on s390x and all other big-endian targets in
>>> Debian. For a full build log on s390x see [1].
>>
>> Gah, my progress display fixes strike again...
>>
>> I think the patch below should fix it, but I could only test it on
>> little-endian systems. Could you please confirm that it indeed works
>> on big-endian as well?
[...]
> I can confirm that your patch fixes the testsuite for me on Debian
> unstable/ppc64 (big-endian).
>
> Tested-By: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Yep, that worked well on the Fedora s390x builders as well
(unsurprisingly).
Thanks!
--
Todd
next prev parent reply other threads:[~2019-10-20 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:37 [BUG]: Testsuite failures on big-endian targets John Paul Adrian Glaubitz
2019-07-31 7:17 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191020001959.GY10893@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=szeder.dev@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.