From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: git@vger.kernel.org, Lars Schneider <larsxschneider@gmail.com>
Subject: Re: [Breakage] t0021 Subtest 15 v2.21.0.-rc2 on NonStop.
Date: Wed, 20 Feb 2019 13:53:03 +0100 [thread overview]
Message-ID: <20190220125303.GQ1622@szeder.dev> (raw)
In-Reply-To: <000f01d4c915$9c4c76a0$d4e563e0$@nexbridge.com>
On Wed, Feb 20, 2019 at 07:12:49AM -0500, Randall S. Becker wrote:
> Sadly I have to report that this subtest breaks on NonStop as of
> v2.21.0-rc2. It succeeds when run with --verbose, but not without,
> making this difficult to diagnose.
That particular test is known to be flaky, see:
https://public-inbox.org/git/000901d4bf98$1ab08fe0$5011afa0$@nexbridge.com/T/#u
next prev parent reply other threads:[~2019-02-20 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 12:12 [Breakage] t0021 Subtest 15 v2.21.0.-rc2 on NonStop Randall S. Becker
2019-02-20 12:53 ` SZEDER Gábor [this message]
2019-02-20 13:55 ` Randall S. Becker
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=20190220125303.GQ1622@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=rsbecker@nexbridge.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).