all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: patch to fix build failure
Date: Sat, 06 May 2023 15:13:23 +0100	[thread overview]
Message-ID: <87cz3d1qoh.fsf@cbaines.net> (raw)
In-Reply-To: <CAJsg1E_7nZAEPbSHfE4=t8GiqekYDpsP7=SzUOa=XGj3qkVq0Q@mail.gmail.com>

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


Andy Tai <atai@atai.org> writes:

> I run into a build failure on python-pyopengl-accelerate which
> prevents guix package -u from proceeding.  I posted a patch to upgrade
> python-pyopengl to the next version, which is sufficient to fix this
> build failure.   The patch is in the issue tracker waiting for Guix QA
> to schedule it for build check...
>
> but I don't know if there is a chicken and egg problem, that Guix QA
> does not seem to schedule recent patches to the main branch for
> builds, and then the committers may not look at the patches which have
> not passed Guix QA, so things are not moving. (My observation, sorry
> if not accurate description)
>
> Again, thanks for all the people working on Guix, including the people
> maintaining Guix QA, highly appreciated.
>
> Just curious if there is any thing that is possible to improve the situation.

Things are moving, but due to a lack of available hardware for doing
builds, things are moving quite slowly.

Currently QA submitting builds for patches is disabled [1] as the
bordeaux build farm is busy catching up after the merge of
core-updates.

1: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=6343780896fcdfdeccfbaf9ef407ceb4641f33b7

You can see an overview of the substitute availability for the master
branch here [2] and currently things are looking good for x86_64-linux.
For powerpc64le-linux and aarch64-linux aren't many builds remaining,
but there are some failing builds leading to the low substitute
availability. For armhf-linux and i686-linux, there are still a lot of
builds to get through, and for i586-gnu, there are failing builds deep
in the graph, so there's fixes needed.

2: https://qa.guix.gnu.org/branch/master

I've got patches I want to see built soon as well, so at some point soon
it'll be the time to start submitting builds for patches again.

On improving the situation though, more hardware we can add to the
bordeaux build farm should help speed things up a lot.

Thanks,

Chris

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

      reply	other threads:[~2023-05-06 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 20:37 patch to fix build failure Andy Tai
2023-05-06 14:13 ` Christopher Baines [this message]

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=87cz3d1qoh.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=atai@atai.org \
    --cc=guix-devel@gnu.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 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.