From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#29634: Hydra fails to honor 'max-silent-time' for early guile build Date: Tue, 12 Dec 2017 17:12:56 -0500 Message-ID: <87h8svd28n.fsf@netris.org> References: <87efo3jq65.fsf@netris.org> <877ett4n7r.fsf@gnu.org> <87y3m8irez.fsf@netris.org> <87po7ks3nf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42336) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOsoP-0002df-Dd for bug-guix@gnu.org; Tue, 12 Dec 2017 17:14:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOsoM-0007VS-8g for bug-guix@gnu.org; Tue, 12 Dec 2017 17:14:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50347) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eOsoM-0007VJ-5H for bug-guix@gnu.org; Tue, 12 Dec 2017 17:14:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eOsoL-0006pI-Tc for bug-guix@gnu.org; Tue, 12 Dec 2017 17:14:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87po7ks3nf.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Dec 2017 10:21:08 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 29634@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> ludo@gnu.org (Ludovic Court=C3=A8s) writes: >> >>> Mark H Weaver skribis: >>> >>>> An early 'guile' build on armhf-linux consistently fails on Hydra, >>>> because the 'timeout' and 'max-silent-time' properties are not honored. >>>> For example: >>>> >>>> https://hydra.gnu.org/build/2391845 >>>> >>>> This is a longstanding issue. In past core-updates cycles, I have >>>> worked around the problem by rebuilding these early 'guile' derivations >>>> from Hydra's command line, passing --timeout and --max-silent-time >>>> manually, and then restarting the many dependency failures. >>>> >>>> It would be good to fix this issue properly. >>>> >>>> My guess is that the build parameters are not honored because there is >>>> no Hydra 'job' associated with this early 'guile'. >>> >>> Exactly. Or maybe there=E2=80=99s one but this early =E2=80=98guile=E2= =80=99 is built as a >>> dependency of another job. >> >> How do you think we should fix this? > > Of course I=E2=80=99d prefer if Guile compile times were shorter. > > Besides, we should probably handle timeouts per-derivation rather than > globally (currently timeout are per-session, see =E2=80=98set-build-optio= ns=E2=80=99). > We could do that by adding a new special value in the environment > variable map of derivation (as is the case for, e.g., > =E2=80=9CexportReferencesGraph=E2=80=9D) that the daemon would honor. It= =E2=80=99s a > rebuild-the-world change though. Sounds good to me. For now, I'll rebuild the early guile for armhf manually. Thanks, Mark