git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'brian m. carlson'" <sandals@crustytoothpaste.net>
Cc: "'Git Mailing List'" <git@vger.kernel.org>
Subject: RE: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh
Date: Thu, 23 May 2019 15:57:31 -0400	[thread overview]
Message-ID: <004e01d511a1$c521a120$4f64e360$@nexbridge.com> (raw)
In-Reply-To: <20190522004825.GC8616@genre.crustytoothpaste.net>

On May 21, 2019 20:48, brian m. carlson wrote:
> To: Randall S. Becker <rsbecker@nexbridge.com>
> Cc: 'Git Mailing List' <git@vger.kernel.org>
> Subject: Re: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh
> 
> 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?

Made no difference. t5401 passed cleanly after a the clean -dxf. I don't know where the breadcrumbs are. I guess it could be something funky in the file system on platform or with bash.


  parent reply	other threads:[~2019-05-23 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 21:47 Randall S. Becker
2019-05-22  0:48 ` brian m. carlson
2019-05-22 13:46   ` Randall S. Becker
2019-05-23 20:05     ` Issues with t7519.19, was " Johannes Schindelin
2019-05-23 20:18       ` Randall S. Becker
2019-05-23 20:55         ` Johannes Schindelin
2019-05-23 19:57   ` Randall S. Becker [this message]
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:
  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='004e01d511a1$c521a120$4f64e360$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    --subject='RE: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh' \
    /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

Code repositories for project(s) associated with this 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).