All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Colin Stagner <ask+git@howdoi.land>
Subject: [PATCH] ci: avoid ubuntu:rolling in most jobs for now
Date: Thu, 05 Feb 2026 13:26:42 -0800	[thread overview]
Message-ID: <xmqqy0l6khkd.fsf@gitster.g> (raw)

We just was hit by buggy uutils dirname in ubuntu:rolling.
Avoid breakage caused by being on the bleeding edge.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---

 * So here is what I have near the merge of "let's test contrib/
   stuff as well" in 'seen' for today's integration to avoid getting
   hit by broken dirname in ubuntu:rolling reported earlier in

    https://lore.kernel.org/git/ef128e1d-dd3e-4573-bfcd-6a98a0a1f394@howdoi.land/

   Until uutils used by ubuntu:rolling stabilizes a bit more, we may
   want to keep a patch like this in our CI jobs.  Or we may offer
   ourselves as a guinea-pig?  I do not have strong preference
   either way.

 .github/workflows/main.yml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index f2e93f5461..0b4567c99f 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -377,10 +377,10 @@ jobs:
       matrix:
         vector:
         - jobname: linux-sha256
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: clang
         - jobname: linux-reftable
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: clang
         - jobname: linux-TEST-vars
           image: ubuntu:20.04
@@ -388,20 +388,20 @@ jobs:
           cc_package: gcc-8
         - jobname: linux-breaking-changes
           cc: gcc
-          image: ubuntu:rolling
+          image: ubuntu:latest
         - jobname: fedora-breaking-changes-meson
           image: fedora:latest
         - jobname: linux-leaks
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: gcc
         - jobname: linux-reftable-leaks
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: gcc
         - jobname: linux-asan-ubsan
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: clang
         - jobname: linux-meson
-          image: ubuntu:rolling
+          image: ubuntu:latest
           cc: gcc
         - jobname: linux-musl-meson
           image: alpine:latest
-- 
2.53.0-181-gfd50f4332d


             reply	other threads:[~2026-02-05 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 21:26 Junio C Hamano [this message]
2026-02-05 21:55 ` [PATCH] ci: avoid ubuntu:rolling in most jobs for now Collin Funk
2026-02-06  7:39 ` Patrick Steinhardt
2026-02-07  4:27   ` Colin Stagner
2026-02-07  4:56     ` Junio C Hamano
2026-02-07  5:35       ` Colin Stagner

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=xmqqy0l6khkd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ask+git@howdoi.land \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.