git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFH] Why do osx CI jobs so unreliable?

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 19, 2026, 00:35 UTC
Message-ID
<xmqqik7fnz90.fsf@gitster.g>

I've been observing that in recent push-out to 'master' and 'next', osx-* jobs in GitHub Actions CI keep running for 6 hours and get killed.

What is troubling is that this seems to be very flaky. For example, https://github.com/git/git/actions/runs/27778820659 is testing 95e20213 (Hopefully final batch before -rc2, 2026-06-17) which got killed after wasting 6 hours in osx-clang and osx-gcc jobs.

https://github.com/git/git/actions/runs/27790036076 is testing the same 'master', with a patch to .github/workflows/main.yml to remove everything except for config and osx-* jobs, which succeeded within 30 minutes.

Stumped...
Next: Patrick Steinhardt
Message 1 of 2 in “[RFH] Why do osx CI jobs so unreliable?”
  1. Junio C HamanoJun 19, 2026
  2. Patrick SteinhardtJun 19, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.