From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH 3/3] ci: stop installing "gcc-13" for osx-gcc
Date: Fri, 17 May 2024 10:25:20 +0200 [thread overview]
Message-ID: <ZkcUcPhrTrbSbZO8@tanuki> (raw)
In-Reply-To: <20240517081132.GA1517321@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Fri, May 17, 2024 at 04:11:32AM -0400, Jeff King wrote:
> On Thu, May 16, 2024 at 02:36:19PM +0200, Patrick Steinhardt wrote:
[snip]
> One can guess that scalar is in waitpid() waiting for git-fetch. But
> what's fetch waiting on? The other side of upload-pack is dead.
> According to lsof, it does have a unix socket open to fsmonitor. So
> maybe it's trying to read there?
That was also my guess. I tried whether disabling fsmonitor via
`core.fsmonitor=false` helps, but that did not seem to be the case.
Either because it didn't have the desired effect, or because the root
cause is not fsmonitor. No idea which of both it is.
> Curiously killing fsmonitor doesn't un-stick fetch, and nor does killing
> fetch unstick scalar. So either my guesses above are wrong, or there's
> something else weird causing them to hang.
>
> I imagine there may be better tools to poke at things, but I'm at the
> limits of my macOS knowledge. But maybe the recipe above is enough for
> somebody more clueful to recreate and investigate the situation (it
> probably would also be easy to just run the --stress script locally if
> somebody actually has a mac).
Let's hope it is :)
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-17 8:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 16:22 [PATCH 0/3] un-breaking osx-gcc ci job Jeff King
2024-05-09 16:23 ` [PATCH 1/3] ci: drop mention of BREW_INSTALL_PACKAGES variable Jeff King
2024-05-09 16:24 ` [PATCH 2/3] ci: avoid bare "gcc" for osx-gcc job Jeff King
2024-05-10 7:00 ` Patrick Steinhardt
2024-05-10 20:16 ` Jeff King
2024-05-10 20:32 ` Kyle Lippincott
2024-05-10 20:48 ` Junio C Hamano
2024-05-10 22:02 ` Jeff King
2024-05-10 22:47 ` Junio C Hamano
2024-05-11 17:21 ` Patrick Steinhardt
2024-05-16 7:19 ` Jeff King
2024-05-16 7:27 ` Jeff King
2024-05-16 9:54 ` Patrick Steinhardt
2024-05-17 8:19 ` Jeff King
2024-05-17 8:33 ` Patrick Steinhardt
2024-05-17 16:59 ` Junio C Hamano
2024-05-23 9:10 ` Jeff King
2024-05-23 15:35 ` Junio C Hamano
2024-05-09 16:25 ` [PATCH 3/3] ci: stop installing "gcc-13" for osx-gcc Jeff King
2024-05-10 7:00 ` Patrick Steinhardt
2024-05-10 20:13 ` Jeff King
2024-05-11 7:17 ` Patrick Steinhardt
2024-05-16 12:36 ` Patrick Steinhardt
2024-05-17 8:11 ` Jeff King
2024-05-17 8:25 ` Patrick Steinhardt [this message]
2024-05-17 11:30 ` Patrick Steinhardt
2024-05-26 6:34 ` Philip
2024-05-26 19:23 ` Junio C Hamano
2024-05-27 5:12 ` Patrick Steinhardt
2024-05-29 9:27 ` Jeff King
2024-05-09 16:52 ` [PATCH 0/3] un-breaking osx-gcc ci job Junio C Hamano
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=ZkcUcPhrTrbSbZO8@tanuki \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=stolee@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.
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).