git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: Jeffrey Walton <noloader@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Git 2.26.2 and failed self tests on OS X
Date: Mon, 4 May 2020 13:18:06 -0400	[thread overview]
Message-ID: <CAPig+cSPXqvFg3-25aDzptuVOHmqOcnmsCKHgjMB9poPyJR2gw@mail.gmail.com> (raw)
In-Reply-To: <20200504165214.GF86805@Carlos-MBP>

On Mon, May 4, 2020 at 12:52 PM Carlo Marcelo Arenas Belón
<carenas@gmail.com> wrote:
> On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:
> > I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6
> > and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are
> > failing.
> >
> > The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.
>
> if the problem is the bash version but you can build/install a newer one that
> doesn't have this problem [...]

My OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce
these failures, so it seems fairly unlikely that the problem Jeffrey
is seeing isn't tied to Bash.

  reply	other threads:[~2020-05-04 17:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  7:03 Git 2.26.2 and failed self tests on OS X Jeffrey Walton
2020-05-04 15:39 ` Eric Sunshine
2020-05-04 16:52 ` Carlo Marcelo Arenas Belón
2020-05-04 17:18   ` Eric Sunshine [this message]
2020-05-04 19:08     ` Torsten Bögershausen
2020-05-04 19:19       ` Eric Sunshine
2020-05-04 19:20       ` Jeffrey Walton
2020-05-04 20:19         ` Torsten Bögershausen
2020-05-04 20:30           ` Jeffrey Walton
2020-05-04 21:39             ` Jeffrey Walton
2020-05-05  4:10               ` Torsten Bögershausen
2020-05-05 12:26                 ` Philippe Blain
2020-05-06 20:36                   ` Jeffrey Walton
2020-05-07  4:12                     ` Jeffrey Walton
2020-05-06 20:48                 ` Jeffrey Walton

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=CAPig+cSPXqvFg3-25aDzptuVOHmqOcnmsCKHgjMB9poPyJR2gw@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=noloader@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 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 NNTP newsgroup(s).