From: Junio C Hamano <gitster@pobox.com>
To: Colin Stagner <ask+git@howdoi.land>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
Patrik Weiskircher <patrik@pspdfkit.com>,
Adam Dinwoodie <adam@dinwoodie.org>
Subject: Re: Re* [RFH] adding test coverage for contrib/ in CI jobs
Date: Thu, 05 Feb 2026 12:54:19 -0800 [thread overview]
Message-ID: <xmqq4inulxms.fsf@gitster.g> (raw)
In-Reply-To: <xmqqikcbm9ew.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 05 Feb 2026 08:39:51 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Colin Stagner <ask+git@howdoi.land> writes:
> ...
>> At least some of the subtree failures on linux-reftable, such as
>>
>> <https://github.com/git/git/actions/runs/21617099884/job/62298228602#step:10:421>
>>
>> are actually due to a bug in ubuntu:rolling's "dirname" implementation.
>
> Ahh, rust bites again?
>
> Is there /etc/alternatives/dirname like /etc/alternatives/sudo that
> we used in fddb4842 (ci: fix broken jobs on Ubuntu 25.10 caused by
> switch to sudo-rs(1), 2025-10-10) to work a breakage around, I have
> to wonder...
So I tried a custom CI run that has
* a temporary patch that demotes ubuntu:rolling to ubuntu:latest in
GitHub workflows
* your subtree test fix to use the hardcoded 'main'
* a similar fix for diff-highlight test <xmqq7bstsemv.fsf@gitster.g>
* a change to run "make test" in contrib/* directories <xmqqjywuyhu9.fsf@gitster.g>
on top of 'master'. Everything seems to be happy.
https://github.com/git/git/actions/runs/21726017981
next prev parent reply other threads:[~2026-02-05 20:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 12:09 [PATCH] subtree: validate --prefix against commit in split Pushkar Singh
2026-01-15 12:24 ` [PATCH v2] " Pushkar Singh
2026-01-15 16:30 ` Junio C Hamano
2026-01-15 17:52 ` [PATCH v3] " Pushkar Singh
2026-02-02 18:54 ` Josh Steadmon
2026-02-02 19:10 ` Junio C Hamano
2026-02-02 21:07 ` Junio C Hamano
2026-02-03 15:30 ` [RFH] adding test coverage for contrib/ in CI jobs Junio C Hamano
2026-02-03 17:06 ` Re* " Junio C Hamano
2026-02-03 23:09 ` Junio C Hamano
2026-02-04 4:38 ` Colin Stagner
2026-02-04 19:55 ` Junio C Hamano
2026-02-05 6:05 ` Colin Stagner
2026-02-05 16:39 ` Junio C Hamano
2026-02-05 20:54 ` Junio C Hamano [this message]
2026-02-03 21:26 ` Junio C Hamano
2026-02-03 21:53 ` Jeff King
2026-02-03 16:48 ` [PATCH v4] subtree: validate --prefix against commit in split Pushkar Singh
2026-02-03 17:37 ` 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=xmqq4inulxms.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adam@dinwoodie.org \
--cc=ask+git@howdoi.land \
--cc=git@vger.kernel.org \
--cc=patrik@pspdfkit.com \
--cc=ps@pks.im \
/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