From: Jeff Hostetler <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>,
Jeff Hostetler <firstname.lastname@example.org>,
Subject: Re: [CI]: Is t7527 known to be flakey?
Date: Fri, 20 Jan 2023 10:23:29 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On 1/19/23 9:52 PM, Junio C Hamano wrote:
> The said test failed its linux-musl job in its first attempt, but
> re-running the failed job passed.
> (seen@e096683 attempt #1 linux-musl)
> (seen@e096683 attempt #2 linux-musl)
This is on Linux, so it would be using the linux inotify backend.
Let me add Eric to the "To:" line for visibility. And see if he
has experienced this during his development of it.
I've not looked at the inotify code so I can't say if there are
races there or not. Tests that move directories feel like good
candidates for race conditions -- since the daemon doesn't get a
recursive view of the tree with inotify() and must simulate that
and manage the individual directories, but again I don't want to
next prev parent reply other threads:[~2023-01-20 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 2:52 [CI]: Is t7527 known to be flakey? Junio C Hamano
2023-01-20 15:23 ` Jeff Hostetler [this message]
2023-01-20 15:40 ` Junio C Hamano
2023-01-21 10:23 ` SZEDER Gábor
2023-01-23 16:56 ` Jeff Hostetler
2023-01-23 18:12 ` SZEDER Gábor
2023-01-25 19:02 ` Jeff Hostetler
2023-01-25 21:12 ` SZEDER Gábor
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: 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 \
* 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).