GNU bug report logs - #77340
Request for merging "mesa-updates" branch

Previous Next

To reply to this bug, email your comments to 77340 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: Request for merging "mesa-updates" branch
Date: Fri, 28 Mar 2025 15:34:38 +0000

Hi Guix,

I have pushed the series at https://issues.guix.gnu.org/77339 to the
mesa-updates branch and actually the build on Berlin is done other than
a handful. Will have to see how coverage on non-x86 looks (x86_64 is
good) but the fact that it finished on Berlin and looks similar to
master in overall percentage is a good sign?

I see we have many branches waiting, are they all world rebuilds? What
are their statuses?

I think this one is ready as long as substitutes have built.

Thanks!
John

Message #8 received at 77340 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: 77340 <at> debbugs.gnu.org
Subject: Re: bug#77340: Request for merging "mesa-updates" branch
Date: Fri, 04 Apr 2025 01:51:18 +0000

On Fri, Mar 28, 2025 at 03:34 PM, John Kehayias wrote:

> Hi Guix,
>
> I have pushed the series at https://issues.guix.gnu.org/77339 to the
> mesa-updates branch and actually the build on Berlin is done other than
> a handful. Will have to see how coverage on non-x86 looks (x86_64 is
> good) but the fact that it finished on Berlin and looks similar to
> master in overall percentage is a good sign?
>
> I see we have many branches waiting, are they all world rebuilds? What
> are their statuses?
>
> I think this one is ready as long as substitutes have built.
>
> Thanks!
> John

Rebased, added <https://issues.guix.gnu.org/76337>, and updated mesa to
25.0.3.

John

Message #11 received at 77340 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: 77340 <at> debbugs.gnu.org
Subject: Re: bug#77340: Request for merging "mesa-updates" branch
Date: Sun, 1 Jun 2025 11:36:42 +0200

Hello,

as this branch is getting closer to the front, I have rebased it on
   e29c57ab81517424b03579147910553d92246212 .

Andreas

Message #16 received at 77340 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: 76899 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>,
 Greg Hogan <code <at> greghogan.com>, 77340 <at> debbugs.gnu.org
Subject: Re: bug#77340: Request for merging "mesa-updates" branch
Date: Thu, 5 Jun 2025 10:43:57 +0200

Hello,

while waiting for the c++-team branch to be fixed, I have passed the
mesa-updates branch to the front after rebasing it on commit
027a47787f8dcf6651a1c20c5b475376defe6d6b .

Please keep observing it and merge it when it is ready.

I am not sure if QA is currently keeping up with the branches, but it
is also evaluated by CI at
   https://ci.guix.gnu.org/jobset/mesa-updates

Thanks,

Andreas

Message #19 received at 77340 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76899 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>,
 Greg Hogan <code <at> greghogan.com>, 77340 <at> debbugs.gnu.org
Subject: Re: bug#77340: Request for merging "mesa-updates" branch
Date: Sun, 08 Jun 2025 19:53:41 +0000

Hi Andreas et al.

On Thu, Jun 05, 2025 at 10:43 AM, Andreas Enge wrote:

> Hello,
>
> while waiting for the c++-team branch to be fixed, I have passed the
> mesa-updates branch to the front after rebasing it on commit
> 027a47787f8dcf6651a1c20c5b475376defe6d6b .
>

Thanks! I just rebased on 199fd26ab268d4f26cebcb39e844fe4ff9bea9bc (had
a checkmark on data services) and pushed another mesa update as they had
an emergency bugfix release (issue with latest AMD cards).

Prior to that the coverage on QA was about the same as master.

> Please keep observing it and merge it when it is ready.
>

So I can go ahead and merge this after this update builds then?

> I am not sure if QA is currently keeping up with the branches, but it
> is also evaluated by CI at
>    https://ci.guix.gnu.org/jobset/mesa-updates
>

Yup, I've been keeping an eye on there whenever I'm working on this
branch, at least to see x86/x86_64 builds (always need to wait for
Bordeaux for others).

> Thanks,
>
> Andreas

A thanks for helping manage the branches!
John

Message #24 received at 77340 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: 76899 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>,
 Greg Hogan <code <at> greghogan.com>, 77340 <at> debbugs.gnu.org
Subject: Re: bug#77340: Request for merging "mesa-updates" branch
Date: Mon, 9 Jun 2025 16:43:37 +0200

Hello,

Am Sun, Jun 08, 2025 at 07:53:41PM +0000 schrieb John Kehayias:
> So I can go ahead and merge this after this update builds then?

yes, please do, close the bug and delete the branch (and keep us in cc).
This is assuming all goes well :)
There seem to be problems with CI as you reported, and the previous
evaluation had lots of failing packages, but they looked rather spurious
than real failures.

On QA, it has taken a while until the mesa-updates branch went to the
front, although I had given "block" instructions to debbugs - maybe
Chris had to change some code to take multiple blocks into account?
No, apparently blocking is not transitive - I see he has added an
explicit block yesterday.

So QA is working full-speed on the branch.
There are a few failing packages:
   https://qa.guix.gnu.org/branch/mesa-updates/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
I will let you judge whether these are more than random failures,
and if they are related to mesa, whether they should be repaired on
the branch or whether this can wait until master.

Thanks,

Andreas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.