all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48024@debbugs.gnu.org
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Mon, 03 May 2021 23:01:22 -0400	[thread overview]
Message-ID: <87h7jjnqw2.fsf@netris.org> (raw)
In-Reply-To: <87fsz3jx58.fsf@disroot.org>

Hi,  [added Efraim Flashner to the CC list]

Bone Baboon <bone.baboon@disroot.org> writes:

> Thank you for your helpful response.
>
> Would a patch like this that addresses test timeouts be good to have in
> the Guix repository?  It would help other Guix users who also run into
> test timeouts when building glib.

Good question!  The problem is that applying this patch would entail
rebuilding every package that depends on 'glib' for i686-linux, which is
likely on the order of thousands of packages.  By policy, we don't make
changes that require so many rebuilds on our 'master' branch.  Instead,
such changes must be made on 'core-updates', or possibly 'staging',
which are merged into 'master' a few times a year.

The plan seems to have been to remove the conditional on our
'core-updates' branch, so that the 'increase-test-timeout' phase would
be included on *all* architectures.  See the comment above the code:

  <https://git.sv.gnu.org/cgit/guix.git/tree/gnu/packages/glib.scm?id=b9fb13b28437a254683273094f189396a6e1421d#n231>

However, I see now that the 'increase-test-timeout' phase was recently
completely _removed_ by Efraim on our 'core-updates' branch a couple of
weeks ago, in the following commit:

  <https://git.sv.gnu.org/cgit/guix.git/commit/?h=core-updates&id=a24562af52d2f318c9e17be73393ddb4bd9e347c>

Efraim: What was the rationale for removing that phase?

I think it would be good to keep that phase, for the benefit of users
building 'glib' on slower machines.  I think the intent was to remove
the conditional, but to keep the body that's within the conditional.

What do you think?

      Regards,
        Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




  parent reply	other threads:[~2021-05-04  3:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  3:35 bug#48024: glib-2.62.6 build fails i686 Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:26 ` raingloom
2021-04-27 19:25   ` Bone Baboon via Bug reports for GNU Guix
2021-04-28  3:23     ` Mark H Weaver
2021-05-03 22:00       ` Bone Baboon via Bug reports for GNU Guix
2021-05-04  0:38         ` Leo Famulari
2021-05-04  3:01         ` Mark H Weaver [this message]
2021-05-04  6:18           ` Efraim Flashner
2021-05-04 20:01             ` Mark H Weaver
2021-05-04 20:08               ` Mark H Weaver
2021-05-04 22:52               ` Bone Baboon via Bug reports for GNU Guix
2021-05-05  8:38               ` Efraim Flashner
2021-05-05 21:15                 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  0:20                   ` Mark H Weaver
2021-05-06  0:35                     ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  6:45                   ` Efraim Flashner
2021-05-06  9:06                     ` Bengt Richter
2021-05-06 17:44                     ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:46                       ` Mark H Weaver
2021-05-08 13:26                         ` Bengt Richter
2022-03-18  2:26                     ` Maxim Cournoyer
2021-05-04  3:56         ` Mark H Weaver
2021-05-05 16:34           ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  8:46             ` Mark H Weaver
2021-05-06 19:36               ` Bone Baboon via Bug reports for GNU Guix

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=87h7jjnqw2.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=48024@debbugs.gnu.org \
    --cc=bone.baboon@disroot.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.