From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: t3206-range-diff failures on non x86 arches
Date: Wed, 01 Mar 2023 12:01:58 -0800 [thread overview]
Message-ID: <xmqqv8jkmea1.fsf@gitster.g> (raw)
In-Reply-To: <Y/+paI8WGSmEbv/w@pobox.com> (Todd Zullinger's message of "Wed, 1 Mar 2023 14:37:12 -0500")
Todd Zullinger <tmz@pobox.com> writes:
> Junio C Hamano wrote:
>> A release candidate Git v2.40.0-rc1 is now available for testing at
>> the usual places. It is comprised of 458 non-merge commits since
>> v2.39.0, contributed by 78 people, 30 of which are new faces [*].
>
> On Fedora, rc1 fails most tests in t3206-range-diff.sh on 3
> of the 5 supported architectures: aarch64, ppc64le, and
> s390x. These tests succeed on i686 and x86_64. They passed
> on all arches with rc0.
Sounds like something d9165bef (range-diff: avoid compiler warning
when char is unsigned, 2023-02-28) may fix. Can you try merging it
to rc1 yourself and see how the result does?
Thanks.
next prev parent reply other threads:[~2023-03-01 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 17:40 [ANNOUNCE] Git v2.40.0-rc1 Junio C Hamano
2023-03-01 19:37 ` t3206-range-diff failures on non x86 arches (was: [ANNOUNCE] Git v2.40.0-rc1) Todd Zullinger
2023-03-01 19:52 ` Jeff King
2023-03-01 20:01 ` Junio C Hamano [this message]
2023-03-01 20:21 ` t3206-range-diff failures on non x86 arches Todd Zullinger
2023-03-01 21:05 ` Todd Zullinger
2023-03-01 21:36 ` Junio C Hamano
2023-03-14 11:08 ` Teng Long
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=xmqqv8jkmea1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=tmz@pobox.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.