mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
To: "Randall S. Becker" <>
Cc: "'brian m. carlson'" <>,
	'Git Mailing List' <>
Subject: Issues with t7519.19, was RE: [Breakage] 2.22.0-rc1
Date: Thu, 23 May 2019 22:05:37 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <004301d510a4$bbe362e0$33aa28a0$>

Hi Randall,

On Wed, 22 May 2019, Randall S. Becker wrote:

> On May 21, 2019 20:48, brian m. carlson wrote:
> > To: Randall S. Becker <>
> > Cc: 'Git Mailing List' <>
> > Subject: Re: [Breakage] 2.22.0-rc1
> >
> > On 2019-05-21 at 21:47:54, Randall S. Becker wrote:
> > > When running the test in isolation, it passes without incident
> > > whether or not --verbose is used. So far, this only occurs on the
> > > first run through. I wanted to report it, based on the inconsistency
> > > of results. This is not the first time tests have acted in this
> > > fashion, and I realize it is difficult to do anything about it
> > > without being able to recreate
> > the situation.
> >
> > Does running git clean -dxf cause it to be reproducible?
> I will give it a go. Having exactly the same behaviour in t7519 subtest
> 19. I wonder whether there are breadcrumbs not being cleaned up. Will
> report back when I am able - may take a day or so.

I fear that t7519's problems are *completely* unrelated to the t5401 issue
you reported earlier. I hunted the t7519 problems down today, and I could
imagine that these patches fix your t7519, too:


  reply	other threads:[~2019-05-23 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 21:47 [Breakage] 2.22.0-rc1 Randall S. Becker
2019-05-22  0:48 ` brian m. carlson
2019-05-22 13:46   ` Randall S. Becker
2019-05-23 20:05     ` Johannes Schindelin [this message]
2019-05-23 20:18       ` Issues with t7519.19, was " Randall S. Becker
2019-05-23 20:55         ` Johannes Schindelin
2019-05-23 19:57   ` Randall S. Becker
2019-05-23 21:00     ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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).