Re: [RFH] Why do osx CI jobs so unreliable?
- From
Michael Montalbo <mmontalbo@gmail.com>
- Date
- Jun 26, 2026, 23:26 UTC
- Message-ID
- <CAC2QwmLkHUymvtYbjY8aQO9_VogvaSXdbb1_DSZtcBttGfN0tg@mail.gmail.com>
- In-Reply-To
- <aj5ZaZK7xylfs4Xw@pks.im>
On Fri, Jun 26, 2026 at 3:50 AM Patrick Steinhardt <ps@pks.im> wrote:
> The bug manifests both with HTTP/1.1 and HTTP/2 though, so this wouldn't > fully fix the flakes we see, right?
Yes you are right. The linked fix would just prevent the hanging after timeout for HTTP/2 tests, but still leaves HTTP/1.1 fakes.
> I was also wondering whether we can maybe work around the issue by > increasing the Apache timeout value. That sounds like an easy potential > solution to try, and from all we've discovered so far it doesn't feel > like this is something we can address on the Git side.
I think Peff and Patrick's suggestion to just increase the Apache timeout makes sense. I ran some experiments using a really long timeout with an artificially slowed down CI runner and all the jobs made progress (if slowly) without stalling, and eventually completed successfully:
https://github.com/mmontalbo/git/actions/runs/28267019651
I haven't spent a lot of time trying to figure out what the right timeout value should be. An hour definitely seems like overkill, with something on the order of 5-10 minutes seeming more reasonable, but I don't have a principled number.