GNU bug report logs -
#77340
Request for merging "mesa-updates" branch
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 77340 in the body.
You can then email your comments to 77340 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Fri, 28 Mar 2025 15:35:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
John Kehayias <john.kehayias <at> protonmail.com>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Fri, 28 Mar 2025 15:35:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Fri, 04 Apr 2025 01:52:03 GMT)
Full text and
rfc822 format available.
Message #8 received at 77340 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Sun, 01 Jun 2025 09:37:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 77340 <at> debbugs.gnu.org (full text, mbox):
Hello,
as this branch is getting closer to the front, I have rebased it on
e29c57ab81517424b03579147910553d92246212 .
Andreas
Added indication that bug 77340 blocks76899
Request was from
Andreas Enge <andreas <at> enge.fr>
to
control <at> debbugs.gnu.org
.
(Thu, 05 Jun 2025 08:32:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Thu, 05 Jun 2025 08:45:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 77340 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Sun, 08 Jun 2025 19:54:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 77340 <at> debbugs.gnu.org (full text, mbox):
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
Added indication that bug 77340 blocks75518
Request was from
Christopher Baines <mail <at> cbaines.net>
to
control <at> debbugs.gnu.org
.
(Sun, 08 Jun 2025 21:07:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Mon, 09 Jun 2025 14:44:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 77340 <at> debbugs.gnu.org (full text, mbox):
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
Reply sent
to
John Kehayias <john.kehayias <at> protonmail.com>
:
You have taken responsibility.
(Wed, 11 Jun 2025 22:42:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
John Kehayias <john.kehayias <at> protonmail.com>
:
bug acknowledged by developer.
(Wed, 11 Jun 2025 22:42:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 77340-done <at> debbugs.gnu.org (full text, mbox):
Hi Andreas et al,
On Mon, Jun 09, 2025 at 04:43 PM, Andreas Enge wrote:
> 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.
>
I've gone ahead and merged mesa-updates after Efraim (added to CC) made
some fixes for riscv64-linux (though this isn't set to build on
QA/mesa-updates so substitutes will only build now on Berlin/master).
I'll be keeping an eye for any failures or reports of trouble, hopefully
just some random leaf packages at most.
> 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.
>
It has been hard to investigate failures directly from the Berlin CI
jobset due to webfront end/build processing issues where. I had reports
of at least one user on IRC that has used the branch fine on their
machine, and I've checked my own manifests as well. Usually (hopefully
not famous last words!) there isn't much happening, but it would be good
to have people with different hardware in the future to test pre-merge,
especially older hardware.
I didn't spot anything that looked critical or necessarily related to
these changes, but I'll be sure to be available for any fixes. Overall
substitute coverage was about the same as master in the last few days so
I don't anticipate much action, hopefully.
> Thanks,
>
> Andreas
Thanks for helping coordinate!
I really better create a mesa/graphics team and get this on a regular
schedule. It is a pretty straightforward branch and packages when doing
it a regular pace to keep relatively up to date with upstream.
John
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77340
; Package
guix-patches
.
(Thu, 12 Jun 2025 08:40:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 77340 <at> debbugs.gnu.org (full text, mbox):
Hello John,
thanks for pushing this through (figuratively and literally ;-))!
Am Wed, Jun 11, 2025 at 10:41:44PM +0000 schrieb John Kehayias:
> I've gone ahead and merged mesa-updates after Efraim (added to CC) made
> some fixes for riscv64-linux (though this isn't set to build on
> QA/mesa-updates so substitutes will only build now on Berlin/master).
I have also deleted the mesa-updates branch. This follows our policy and
avoids us ending up with old branches of which we have forgotten whether
they are work in progress or already merged. Please feel free to branch off
from master again at any time.
Packages for riscv64 are also built on the bordeaux build farm, with a
decent coverage:
https://qa.guix.gnu.org/branch/master
Cheers,
Andreas
Removed indication that bug 77340 blocks
Request was from
Andreas Enge <andreas <at> enge.fr>
to
control <at> debbugs.gnu.org
.
(Fri, 13 Jun 2025 09:12:02 GMT)
Full text and
rfc822 format available.
Removed indication that bug 77340 blocks
Request was from
Andreas Enge <andreas <at> enge.fr>
to
control <at> debbugs.gnu.org
.
(Fri, 13 Jun 2025 09:12:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 11 Jul 2025 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.