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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#70178: closed (Request for merging "mesa-updates" branch)
Date: Wed, 17 Apr 2024 05:26:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 17 Apr 2024 05:25:13 +0000
with message-id <87zfts1ryj.fsf_-_ <at> protonmail.com>
and subject line Re: bug#70178: Request for merging "mesa-updates" branch
has caused the debbugs.gnu.org bug report #70178,
regarding Request for merging "mesa-updates" branch
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
70178: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70178
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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: Thu, 04 Apr 2024 05:55:08 +0000

Hi Guix,

I submitted a bunch of patches to mesa-updates a few days ago. From what I can tell things have gone well on x86_64, with most of the "new" failures listed are compared to previous mesa-updates and are ones broken on master too. A few failed from some time issue on hydra 128. And a few were legitimate failures which I have fixed. I'll go through again and make sure I didn't miss anything. I've been using this branch locally for a few things without issues so far.

So...I'm guessing the main thing is to wait for non-x86 coverage. Is there a way to see that on Bordeaux? As always, please report any issues, but hopefully this will be good to go once builds are done.

John

[Message part 3 (message/rfc822, inline)]

From: John Kehayias <john.kehayias <at> protonmail.com>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 70178-done <at> debbugs.gnu.org, Simon Streit <simon <at> netpanic.org>
Subject: Re: bug#70178: Request for merging "mesa-updates" branch
Date: Wed, 17 Apr 2024 05:25:13 +0000

Hello,

On Mon, Apr 15, 2024 at 11:32 AM, Christopher Baines wrote:

> Christopher Baines <mail <at> cbaines.net> writes:
>
>> John Kehayias via Guix-patches via <guix-patches <at> gnu.org> writes:
>>
>>> I submitted a bunch of patches to mesa-updates a few days ago. From
>>> what I can tell things have gone well on x86_64, with most of the
>>> "new" failures listed are compared to previous mesa-updates and are
>>> ones broken on master too. A few failed from some time issue on hydra
>>> 128. And a few were legitimate failures which I have fixed. I'll go
>>> through again and make sure I didn't miss anything. I've been using
>>> this branch locally for a few things without issues so far.
>>>
>>> So...I'm guessing the main thing is to wait for non-x86 coverage. Is
>>> there a way to see that on Bordeaux? As always, please report any
>>> issues, but hopefully this will be good to go once builds are done.
>>
>> The page on QA should show substitute availability [1]. It's probably
>> going to take a week, probably closer to two to get to a reasonable
>> level.
>
> Substitute availability is getting there, it's just i686-linux which is
> lagging behind (which is expected with the limited compute resources
> available).
>
> I've just pushed a merge commit to keep the branch up to date with
> master.

Thanks for helping out. I merged with
2d5736cc3e869fadd2592cc13a8d332fac63b144. i686 is still a bit lower but
seemed to really slow down or pause, even after I gave it another day.
Anyways, hopefully is fine!

Also, thanks Simon for testing and reporting, apologies for not
responding earlier to your message.

Thanks,
John

Previous Next

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