From: Eric Sunshine <sunshine@sunshineco.com>
To: Bennet Huber <bennet.huber@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git commit hangs when run concurrently on macos
Date: Tue, 1 Oct 2024 00:29:58 -0400 [thread overview]
Message-ID: <CAPig+cSBvU8Ne29SpV7fZeRPmU25EPQxxxmE+agyM303kDoPCA@mail.gmail.com> (raw)
In-Reply-To: <CAJ7FMP0RqfUc0TKxJWn+tGq6tRhhABmbpd+xJMc7SRL6F5=JgA@mail.gmail.com>
On Mon, Sep 30, 2024 at 4:58 PM Bennet Huber <bennet.huber@gmail.com> wrote:
> After running this, wait for output to subside, then run `jobs`.
> On my machine, I usually see 5-10 hung "git commit" jobs.
>
> > 3:39:04.020533 run-command.c:758 trace: start_command: /opt/homebrew/opt/git/libexec/git-core/git fsmonitor--daemon run --detach --ipc-threads=8
>
> Setting `USE_FS_MONITOR=false` in the code above consistently results
> in no hung "git commit" commands, which leads me to suspect the
> problem has to do with the fsmonitor feature. It's also a decent,
> though difficult to discover, workaround.
I don't use fsmonitor and haven't particularly been following the
issue, but there are some active threads on the mailing list regarding
fsmonitor hanging on macOS. Perhaps they are relevant to your case.
https://lore.kernel.org/git/20240930194600.GA1805534@coredump.intra.peff.net/T/
https://lore.kernel.org/git/20240509162219.GA1707955@coredump.intra.peff.net/T/
https://lore.kernel.org/git/pull.1802.git.1727577690390.gitgitgadget@gmail.com/T/
prev parent reply other threads:[~2024-10-01 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 20:58 git commit hangs when run concurrently on macos Bennet Huber
2024-10-01 4:29 ` Eric Sunshine [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cSBvU8Ne29SpV7fZeRPmU25EPQxxxmE+agyM303kDoPCA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=bennet.huber@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).