all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Z572 <zhengjunjie@iscas.ac.cn>
Cc: John Kehayias <john.kehayias@protonmail.com>, 73288@debbugs.gnu.org
Subject: [bug#73288] Request for merging "mesa-updates" branch
Date: Sun, 3 Nov 2024 15:02:49 +0200	[thread overview]
Message-ID: <Zyd0efjfhr1QrRN_@3900XT> (raw)
In-Reply-To: <87cyjck50n.fsf@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]

On Sun, Nov 03, 2024 at 06:04:08PM +0800, Z572 wrote:
> John Kehayias via Guix-patches via <guix-patches@gnu.org> writes:
> 
> > Hello Guix,
> >
> > The mesa-updates branch I think is just almost ready for
> > merging. Besides some other fixes and updates, the main series is
> > tracked at <https://issues.guix.gnu.org/73071>. There is an update to
> > add NVK support to mesa for x86_64-linux which I need to review and
> > push (and rebase to get more fixes from master).
> >
> > Coverage looks good for x86_64 and i686 on QA, with powerpc64le as
> > well on Berlin. I worry that aarch64 and others may have stalled out
> > on Bordeaux. Perhaps Efraim can chime in there.
> >
> > With an update for NVK for x86_64, that will take maybe a day to catch
> > up again in builds but tends to be pretty quick. I'm not aware of
> > other blockers.
> >
> > Thanks!
> > John
> 
> maybe is time to merge?
> 
> see https://qa.guix.gnu.org/branch/mesa-updates
> ci       have x86_64-linux 96.3%, i686-linux 87.7%, powerpc64le-linux 85.5%
> bordeaux have x86_64-linux 91.5%, i686-linux 77.8%, armhf-linux 79.4%, aarch64-linux 89.0%.
> 
> Is there anything else in the way?

Comparing them against master and against each other:
x86_64: comparable on ci, slight regression on bordeaux
i686:   comparable on ci, regression on bordeaux (91.8 -> 77.8)
aarch64: comparable on ci, regression on bordeaux (97.0 -> 89.0)
armhf:  slight regression on bordeaux
ppc64le: comparable on ci and bordeaux
riscv64: regression on bordeaux (62.0 -> 28.2)

I feel like bordeaux will catch-up fairly quickly post merge.  However,
we do now have the regression page for bordeaux of master vs
mesa-updates:
https://qa.guix.gnu.org/branch/mesa-updates/package-changes?x86_64-linux-change=blocked&x86_64-linux-change=still-blocked&x86_64-linux-change=unknown-to-blocked&x86_64-linux-change=new-blocked

However, after spot-checking a few of them to see if there are
substitutes (including gnome and openjdk) it looks like it probably just
needs to be sent through again.

It looks okay to me


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-03 13:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  2:38 [bug#73288] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-09-23  5:34 ` Efraim Flashner
2024-09-30  0:11   ` John Kehayias
2024-10-02 20:53 ` Sharlatan Hellseher
2024-10-03  8:56   ` Steve George via Guix-patches
2024-10-04  8:21     ` Ludovic Courtès
2024-10-03  9:01   ` Steve George via Guix-patches
2024-10-19 14:43 ` [bug#73288] Advance in queue Andreas Enge
2024-10-31 19:35 ` [bug#73288] Request for merging "mesa-updates" branch Sharlatan Hellseher
2024-11-03 10:04 ` Z572
2024-11-03 13:02   ` Efraim Flashner [this message]
2024-11-04  2:32     ` John Kehayias via Guix-patches via
2024-11-04 16:50       ` Z572
2024-11-05  4:15         ` John Kehayias via Guix-patches via
2024-11-05 10:35           ` Efraim Flashner
2024-11-05 18:49         ` bug#73288: " John Kehayias via Guix-patches via
2024-11-04  9:33     ` [bug#73288] " Christopher Baines

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

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

  git send-email \
    --in-reply-to=Zyd0efjfhr1QrRN_@3900XT \
    --to=efraim@flashner.co.il \
    --cc=73288@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=zhengjunjie@iscas.ac.cn \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.