all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Efraim Flashner <efraim@flashner.co.il>, 74780-done@debbugs.gnu.org
Subject: bug#74780: Request for merging "mesa-updates" branch
Date: Mon, 06 Jan 2025 02:11:07 +0000	[thread overview]
Message-ID: <87sepw8zex.fsf@protonmail.com> (raw)
In-Reply-To: <87ed1iqy26.fsf@gnu.org>

Hi Ludo’!

On Sat, Jan 04, 2025 at 06:38 PM, Ludovic Courtès wrote:

> Sure.  Please do check the situation at
> <https://ci.guix.gnu.org/jobset/mesa-updates> and how it compares to
> ‘master’.
>

Yes, I've been keeping an eye on that and by overall percentage (from
the Cuirass homepage), the mesa-updates branch has been about equal to
master for a while. Though I know the missing stuff is for non-x86
which we get more of from Bordeaux, which is what I usually try to
wait for, unfortunately harder to tell without the handy QA page
comparison.

> You can check that direct dependents of packages that were upgraded
> still build fine.  For example, “guix build -P1 mesa --no-grafts -n -v1”
> will indicate whether substitutes are available for all of the direct
> dependents of ‘mesa’, meaning that they were successfully built.
>

Oh, the new dependents option for guix build, very nice! I hadn't
tried it before but this is great.

I didn't see something like this built-in (maybe I missed it?) but
seems pretty easy to do a comparison then to another branch. I just
did the same command on my 'master' worktree and compared, to see just
a few minor differences (so I restarted the builds since they didn't
have a clear error).

A little bash-fu could easily have a nice little comparison between
branches using substitute coverage, or maybe we want to add that as an
option directly? Maybe specifying two branches or commits to see what
package names differ (in hash or substitutes)?


> Thanks for working on this!
>
> Ludo’.

Most welcome!

Merged just now: 23231c296fb2c2af8c1c0a6ead1dd6f0833f7c45 to
a65ebe5fad6921dddb165f417761886fc114ad29.

Thanks,
John





      reply	other threads:[~2025-01-06  2:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  6:30 [bug#74780] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-12-20 20:31 ` John Kehayias via Guix-patches via
2024-12-21 16:32   ` Efraim Flashner
2024-12-22  9:19   ` Efraim Flashner
2024-12-29 14:57     ` Ludovic Courtès
2024-12-30  2:46       ` John Kehayias via Guix-patches via
2025-01-04  5:34       ` John Kehayias via Guix-patches via
2025-01-04 17:38         ` Ludovic Courtès
2025-01-06  2:11           ` John Kehayias via Guix-patches via [this message]

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=87sepw8zex.fsf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=74780-done@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=john.kehayias@protonmail.com \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.