GNU bug report logs - #27157
Building Guile 2.2 "times out"

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: tracker <at> debbugs.gnu.org
Subject: bug#27729: closed (guile-2.2.2 fails to build on armhf in
 core-updates (timeout))
Date: Fri, 01 Sep 2017 09:11:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 01 Sep 2017 11:10:08 +0200
with message-id <874lsm7pjj.fsf <at> gnu.org>
and subject line Re: [PATCH] Re: bug#27157: Building Guile 2.2 "times out"
has caused the debbugs.gnu.org bug report #27157,
regarding guile-2.2.2 fails to build on armhf in core-updates (timeout)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
27157: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27157
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
Subject: guile-2.2.2 fails to build on armhf in core-updates (timeout)
Date: Sun, 16 Jul 2017 20:26:23 -0400

On core-updates, apparently all of the armhf builds are
dependency-failed due to a failure to build an early guile-2.2.2
(/gnu/store/z3h8q7qrv20vc361q1ry7j1izbmrvrjh-guile-2.2.2.drv).  The
reason is that the 'max-silent-time' being used for that build is 1
hour, although it should be 10 hours.

In order to get things building again, I've asked Hydra to manually
build this derivation from the command-line, with the needed
--max-silent-time and --timeout settings.  However, it would be good to
find out what's going wrong here, so that we can avoid doing this
manually on every core-updates cycle.

      Mark

[Message part 3 (message/rfc822, inline)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 27157-done <at> debbugs.gnu.org
Subject: Re: [PATCH] Re: bug#27157: Building Guile 2.2 "times out"
Date: Fri, 01 Sep 2017 11:10:08 +0200

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

> From ba078ca1b8efa17fb0b2ee7b4269611c6bb4c3d6 Mon Sep 17 00:00:00 2001
> From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
> Date: Wed, 30 Aug 2017 23:12:12 -0400
> Subject: [PATCH] ui: Remove max-silent-time from the default options.
>
> Having a finite default `max-silent-time' value for scripts such as 'guix
> environment' could lead to timeouts when building subtitutes; this was
> undesirable. This fixes bug #27157.
>
> * guix/scripts/archive.scm (%default-options): Remove max-silent-time entry.
> * guix/scripts/copy.scm (%default-options): Likewise.
> * guix/scripts/environment.scm (%default-options): Likewise.
> * guix/scripts/pack.scm (%default-options): Likewise.
> * guix/scripts/package.scm (%default-options): Likewise.
> * guix/scripts/pull.scm (%default-options): Likewise.
> * guix/scripts/system.scm (%default-options): Likewise.

Good catch!  It was actually a bug, because the doc said that the
daemon’s setting should be honored by default, which was obviously not
the case.

Pushed:

  https://git.savannah.gnu.org/cgit/guix.git/commit/?id=fe55199542590d16aa6ca6a8bfa0fda27903db5c

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.