unofficial mirror of guix-patches@gnu.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: 74780@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#74780] Request for merging "mesa-updates" branch
Date: Mon, 30 Dec 2024 02:46:43 +0000	[thread overview]
Message-ID: <87ed1pnb02.fsf@protonmail.com> (raw)
In-Reply-To: <877c7ir0y8.fsf_-_@gnu.org>

Hi all,

On Sun, Dec 29, 2024 at 03:57 PM, Ludovic Courtès wrote:

> Hey John and all,
>
> It’s the turn of the “mesa-updates” branch to be merged:
>
>   <https://qa.guix.gnu.org/>
>
> :-)
>
> Ludo’.

Thanks for checking in.

I just rebased and pushed. I'll keep an eye on it but didn't notice
any big failures (plenty on earlier evaluations but mostly due to the
python merge from what I can tell).

The question is what the substitute coverage will be like on
non-x86_64-linux. It had already been about 9-10 days from the last
update and didn't seem like much progress. And with QA back up but
very behind, not sure if we expect that to tell us anything soon.

Should I give it a day or so to build the current rebase and then just
merge? From Efraim's local builds and given the nature of the commits,
I don't expect any big surprises.

(Side note: does i686-linux have priority on Berlin or something like
that? The last few weeks I notice many more active i686 builds after a
push with many pending builds. The current evaluation, for instance:
the vast majority of workers are idle, and then the vast majority of
active are i686 builds. Or is that from just generally being behind on
i686 so there's just more of that to do?)

Thanks!
John





      reply	other threads:[~2024-12-30  2:48 UTC|newest]

Thread overview: 6+ 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 [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed1pnb02.fsf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=74780@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).