[bug#74780] Request for merging "mesa-updates" branch

[bug#74780] Request for merging "mesa-updates" branch

[John Kehayias via Guix-patches via]

Hi Guix,

Currently the mesa-updates branch just has a few updates which seem to have built fine (on x86_64 at least), see <https://issues.guix.gnu.org/74779>.

I don't know of other pending changes other than a libva update I'll see about. Perhaps we can do some ungrafting too?

John

[bug#74780] Request for merging "mesa-updates" branch

[John Kehayias via Guix-patches via]

On Wed, Dec 11, 2024 at 06:30 AM, John Kehayias wrote:

> Hi Guix,
>
> Currently the mesa-updates branch just has a few updates which seem to
> have built fine (on x86_64 at least), see
> <https://issues.guix.gnu.org/74779>.
>
> I don't know of other pending changes other than a libva update I'll
> see about. Perhaps we can do some ungrafting too?
>
> John

(CC-ing Efraim after the patch to build the asahi vulkan driver on
aarch64-linux)

I just rebased on master after further updating wayland-protocols and
mesa to their very freshest versions.

Not much else going on here, so maybe just let this build and then merge
to keep things current. Unfortunately the QA page hasn't shown a status
for this branch but I'll check later.

There are discussions about libglvnd support in Mesa I need to chime in
on, so we could tackle that, but not until the new year for me. That
will require a decent number of changes and lots more testing, so my
preference would be to merge this branch when substitutes are available
and then immediately work on libglvnd or whatever else is pending.

John

[bug#74780] Request for merging "mesa-updates" branch

[Efraim Flashner]

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

On Fri, Dec 20, 2024 at 08:31:57PM +0000, John Kehayias wrote:
> On Wed, Dec 11, 2024 at 06:30 AM, John Kehayias wrote:
> 
> > Hi Guix,
> >
> > Currently the mesa-updates branch just has a few updates which seem to
> > have built fine (on x86_64 at least), see
> > <https://issues.guix.gnu.org/74779>.
> >
> > I don't know of other pending changes other than a libva update I'll
> > see about. Perhaps we can do some ungrafting too?
> >
> > John
> 
> (CC-ing Efraim after the patch to build the asahi vulkan driver on
> aarch64-linux)

I didn't test it (I don't have the hardware), but it built just fine and
I assume the Asahi people know what they're doing.

> I just rebased on master after further updating wayland-protocols and
> mesa to their very freshest versions.

I'll rebuild again on a couple of architectures but I don't expect any
issues.

> Not much else going on here, so maybe just let this build and then merge
> to keep things current. Unfortunately the QA page hasn't shown a status
> for this branch but I'll check later.
> 
> There are discussions about libglvnd support in Mesa I need to chime in
> on, so we could tackle that, but not until the new year for me. That
> will require a decent number of changes and lots more testing, so my
> preference would be to merge this branch when substitutes are available
> and then immediately work on libglvnd or whatever else is pending.

That makes sense. Regular smallish updates are one of the reasons for
the team/topic -based branches.

-- 
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 --]

[bug#74780] Request for merging "mesa-updates" branch

[Efraim Flashner]

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

On Fri, Dec 20, 2024 at 08:31:57PM +0000, John Kehayias wrote:
> On Wed, Dec 11, 2024 at 06:30 AM, John Kehayias wrote:
> 
> > Hi Guix,
> >
> > Currently the mesa-updates branch just has a few updates which seem to
> > have built fine (on x86_64 at least), see
> > <https://issues.guix.gnu.org/74779>.
> >
> > I don't know of other pending changes other than a libva update I'll
> > see about. Perhaps we can do some ungrafting too?
> >
> > John
> 
> (CC-ing Efraim after the patch to build the asahi vulkan driver on
> aarch64-linux)
> 
> I just rebased on master after further updating wayland-protocols and
> mesa to their very freshest versions.
> 
> Not much else going on here, so maybe just let this build and then merge
> to keep things current. Unfortunately the QA page hasn't shown a status
> for this branch but I'll check later.
> 
> There are discussions about libglvnd support in Mesa I need to chime in
> on, so we could tackle that, but not until the new year for me. That
> will require a decent number of changes and lots more testing, so my
> preference would be to merge this branch when substitutes are available
> and then immediately work on libglvnd or whatever else is pending.

I built mesa for aarch64, armhf, riscv64 and powerpc64le.  They all
built without any problems.

-- 
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 --]

[bug#74780] Request for merging "mesa-updates" branch

[Ludovic Courtès]

Hey John and all,

It’s the turn of the “mesa-updates” branch to be merged:

  https://qa.guix.gnu.org/

:-)

Ludo’.

[bug#74780] Request for merging "mesa-updates" branch

[John Kehayias via Guix-patches via]

Hi all,

On Sun, Dec 29, 2024 at 03:57 PM, Ludovic Courtès wrote:

> Hey John and all,
>
> It’s the turn of the “mesa-updates” branch to be merged:
>
>   <https://qa.guix.gnu.org/>
>
> :-)
>
> Ludo’.

Thanks for checking in.

I just rebased and pushed. I'll keep an eye on it but didn't notice
any big failures (plenty on earlier evaluations but mostly due to the
python merge from what I can tell).

The question is what the substitute coverage will be like on
non-x86_64-linux. It had already been about 9-10 days from the last
update and didn't seem like much progress. And with QA back up but
very behind, not sure if we expect that to tell us anything soon.

Should I give it a day or so to build the current rebase and then just
merge? From Efraim's local builds and given the nature of the commits,
I don't expect any big surprises.

(Side note: does i686-linux have priority on Berlin or something like
that? The last few weeks I notice many more active i686 builds after a
push with many pending builds. The current evaluation, for instance:
the vast majority of workers are idle, and then the vast majority of
active are i686 builds. Or is that from just generally being behind on
i686 so there's just more of that to do?)

Thanks!
John