From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'Torsten Bögershausen'" <tboegi@web.de>,
"'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>,
"'Jeff King'" <peff@peff.net>,
git@vger.kernel.org
Subject: Re: t0025 flakey?
Date: Fri, 8 Feb 2019 00:57:26 +0100 [thread overview]
Message-ID: <20190207235726.GR10587@szeder.dev> (raw)
In-Reply-To: <001501d4bf06$506b8640$f14292c0$@nexbridge.com>
On Thu, Feb 07, 2019 at 11:58:08AM -0500, Randall S. Becker wrote:
> > The NonStop port has traditionally had issues with t0025, which we tended
> > to ignore because things did work. We wrote those off as bash issues in
> > t0025 since they seemed to be corrected when we picked up a new bash
> > version about a year ago. I will keep monitoring this, particularly when
> 2.21
> > comes out.
>
> FYI: t0020-t0027 all passed on the NonStop port for 2.21.0-rc0 - so no
> issues for us on this one.
Note that t0021 is very likely flaky on NonStop, too:
https://public-inbox.org/git/20190111140408.GC840@szeder.dev/T/#u
next prev parent reply other threads:[~2019-02-07 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 10:25 t0025 flakey? Johannes Schindelin
2019-02-06 10:42 ` SZEDER Gábor
2019-02-06 13:52 ` Johannes Schindelin
2019-02-06 17:15 ` Torsten Bögershausen
2019-02-06 17:39 ` SZEDER Gábor
2019-02-06 18:00 ` Randall S. Becker
2019-02-07 16:58 ` Randall S. Becker
2019-02-07 17:39 ` Junio C Hamano
2019-02-07 23:57 ` SZEDER Gábor [this message]
2019-02-08 10:21 ` Randall S. Becker
2019-02-07 2:00 ` [PATCH] add_to_index(): convert forgotten HASH_RENORMALIZE check Jeff King
2019-02-07 4:18 ` Torsten Bögershausen
2019-02-07 21:00 ` Jeff King
2019-02-07 13:17 ` Johannes Schindelin
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=20190207235726.GR10587@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
--cc=tboegi@web.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).