{"thread":{"id":"65839","subject":"[RFH] Why do osx CI jobs so unreliable?","startedAt":"2026-06-19T00:35:25Z","lastAt":"2026-06-19T14:04:11Z","messageCount":2,"participants":["Junio C Hamano","Patrick Steinhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"545908","messageId":"xmqqik7fnz90.fsf@gitster.g","threadId":"65839","inReplyTo":null,"subject":"[RFH] Why do osx CI jobs so unreliable?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-06-19T00:35:23Z","receivedAt":"2026-06-19T00:35:25Z","isPatch":false,"body":"I've been observing that in recent push-out to 'master' and 'next',\nosx-* jobs in GitHub Actions CI keep running for 6 hours and get\nkilled.\n\nWhat is troubling is that this seems to be very flaky.  For example,\nhttps://github.com/git/git/actions/runs/27778820659 is testing\n95e20213 (Hopefully final batch before -rc2, 2026-06-17) which got\nkilled after wasting 6 hours in osx-clang and osx-gcc jobs.\n\nhttps://github.com/git/git/actions/runs/27790036076 is testing\nthe same 'master', with a patch to .github/workflows/main.yml to\nremove everything except for config and osx-* jobs, which succeeded\nwithin 30 minutes.\n\nStumped...\n"},{"id":"545952","messageId":"ajVMTjniOO-eG8h1@pks.im","threadId":"65839","inReplyTo":"xmqqik7fnz90.fsf@gitster.g","subject":"Re: [RFH] Why do osx CI jobs so unreliable?","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-06-19T14:03:58Z","receivedAt":"2026-06-19T14:04:11Z","isPatch":false,"body":"On Thu, Jun 18, 2026 at 05:35:23PM -0700, Junio C Hamano wrote:\n> I've been observing that in recent push-out to 'master' and 'next',\n> osx-* jobs in GitHub Actions CI keep running for 6 hours and get\n> killed.\n> \n> What is troubling is that this seems to be very flaky.  For example,\n> https://github.com/git/git/actions/runs/27778820659 is testing\n> 95e20213 (Hopefully final batch before -rc2, 2026-06-17) which got\n> killed after wasting 6 hours in osx-clang and osx-gcc jobs.\n> \n> https://github.com/git/git/actions/runs/27790036076 is testing\n> the same 'master', with a patch to .github/workflows/main.yml to\n> remove everything except for config and osx-* jobs, which succeeded\n> within 30 minutes.\n> \n> Stumped...\n\nSo the raw logs have the following trailer:\n\n  2026-06-18T23:53:33.2996180Z Cleaning up orphan processes\n  2026-06-18T23:53:33.7900380Z Terminate orphan process: pid (34022) (git-remote-http)\n  2026-06-18T23:53:33.9848670Z Terminate orphan process: pid (15488) (httpd)\n  2026-06-18T23:53:34.0321490Z Terminate orphan process: pid (13146) (httpd)\n  2026-06-18T23:53:34.0808280Z Terminate orphan process: pid (13145) (httpd)\n  2026-06-18T23:53:34.1212760Z Terminate orphan process: pid (13144) (httpd)\n  2026-06-18T23:53:34.1570160Z Terminate orphan process: pid (13141) (httpd)\n  2026-06-18T23:53:34.1924140Z Terminate orphan process: pid (12553) (bash)\n  2026-06-18T23:53:34.2472970Z Terminate orphan process: pid (12552) (tee)\n  2026-06-18T23:53:34.6547890Z Terminate orphan process: pid (21209) (bash)\n\nSo I strongly suspect that it most be one of the t555* tests.\nFurthermore, the t5551 and t5559 (both of which are actually the same\ntest) are the only test suites that use lib-httpd.sh and which are\nmissing in the job logs.\n\nI have not been able to reproduce this hang on my macOS virtual machine\nthough, and on GitLab I didn't notice a similar hang recently. Maybe\nthis is something that's specific to GitHub's environment...? No idea.\n\nPatrick\n"}]}