From: Christopher Baines <mail@cbaines.net>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 70178-done@debbugs.gnu.org, Simon Streit <simon@netpanic.org>
Subject: [bug#70178] Request for merging "mesa-updates" branch
Date: Wed, 17 Apr 2024 11:52:54 +0100 [thread overview]
Message-ID: <875xwgtg55.fsf@cbaines.net> (raw)
In-Reply-To: <87zfts1ryj.fsf_-_@protonmail.com> (John Kehayias's message of "Wed, 17 Apr 2024 05:25:13 +0000")
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
John Kehayias <john.kehayias@protonmail.com> writes:
> Hello,
>
> On Mon, Apr 15, 2024 at 11:32 AM, Christopher Baines wrote:
>
>> Christopher Baines <mail@cbaines.net> writes:
>>
>>> John Kehayias via Guix-patches via <guix-patches@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!
Great. As for the i686 builds, this was probably slowed down by the
x86_64 builds taking priority after pushing the master merge, since that
triggered builds for both i686 and x86_64.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-04-17 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 5:55 [bug#70178] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-04-04 8:13 ` Christopher Baines
2024-04-15 10:32 ` Christopher Baines
2024-04-17 5:25 ` bug#70178: " John Kehayias via Guix-patches via
2024-04-17 10:52 ` Christopher Baines [this message]
2024-04-04 12:57 ` [bug#70178] " Simon Streit
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=875xwgtg55.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=70178-done@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=simon@netpanic.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).