From: Jeff Hostetler <git@jeffhostetler.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jeff Hostetler <jeffhostetler@github.com>,
edecosta@mathworks.com, git@vger.kernel.org
Subject: Re: [CI]: Is t7527 known to be flakey?
Date: Wed, 25 Jan 2023 14:02:40 -0500 [thread overview]
Message-ID: <7fa84280-db1d-8618-571a-ce0ac7a26135@jeffhostetler.com> (raw)
In-Reply-To: <20230123181216.GB2155@szeder.dev>
On 1/23/23 1:12 PM, SZEDER Gábor wrote:
> On Mon, Jan 23, 2023 at 11:56:53AM -0500, Jeff Hostetler wrote:
>> Was this on Linux or MacOS ?
>
> On an average-ish Linux (an Ubuntu LTS variant). So the issue is not
> specific to musl.
>
OK, thanks. I wasn't worried about "musl", but rather whether
you were running the stress test on a Linux or Mac.
Since they have different backends (inotify vs FSEvent) and all
the code that touches the filesystem is different, it would best
to start on the correct OS when trying to repro it.
Can you tell from your stess test whether the fsmonitor-daemon
is crashing? (It might be subtle since the daemon is auto-started
if necessary, so it might be crashing and silently getting restarted
by the next command.)
I ask because a SIGPIPE in the client would make me think that the
server suddenly closed the connection unexpectedly, like if it had
SIGSEGV'd or something.
I won't have time to spin up a Linux VM until next week, so I
won't be able to investigate this for a bit.
Jeff
next prev parent reply other threads:[~2023-01-25 19:02 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
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 [this message]
2023-01-25 21:12 ` SZEDER Gábor
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=7fa84280-db1d-8618-571a-ce0ac7a26135@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=edecosta@mathworks.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhostetler@github.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).