git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>, git@vger.kernel.org
Subject: Re: t0021-conversion: flaky filter process test
Date: Tue, 15 Jan 2019 14:44:51 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1901151442420.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190111140408.GC840@szeder.dev>

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Hi,

On Fri, 11 Jan 2019, SZEDER Gábor wrote:

> [...]
> 
> Now, in our tests commands are executed in rapid succession, so it's
> highly probable that those files are racily clean, and, consequently,
> 'git checkout' has to look at the contents of the files, meaning that
> it has to run the clean filter process, and then all is well: that's
> why the test succeeds most of the time.  Occasionally, however, the
> commands are executed slow enough or just at the right moment that the
> files are really clean, and 'git checkout' won't bother starting the
> clean filter process, which then won't write a 'debug.log' file,
> resulting in the above failure.

We had a similar problem in some of the VFS4Git tests, and solved it by
using `test-tool chmtime -60 .git/index`. Maybe the same strategy works
here?

Ciao,
Dscho

      reply	other threads:[~2019-01-15 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 14:04 t0021-conversion: flaky filter process test SZEDER Gábor
2019-01-15 13:44 ` Johannes Schindelin [this message]

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=nycvar.QRO.7.76.6.1901151442420.41@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@gmail.com \
    --cc=szeder.dev@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. 
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).