unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 27157@debbugs.gnu.org
Subject: bug#27157: Building Guile 2.2 "times out"
Date: Wed, 31 May 2017 13:44:22 +0200	[thread overview]
Message-ID: <878tld2quh.fsf@elephly.net> (raw)
In-Reply-To: <871sr5sm11.fsf@gmail.com>


Hi Maxim,

> I'm not sure where this timeout value can be configured, but clearly it
> shouldn't be 1 hour since 2 cores of an i5 intel class processor can't
> manage to build it under 1 hour.

for the guile-2.2 package I see that this is part of the package
definition:

    (properties '((timeout . 72000)               ;20 hours
                  (max-silent-time . 10800)))     ;3 hours (needed on ARM)

We do this so that we can build it on Hydra.
You can override the max silent time:

    guix build --max-silent-time=9999999 guile

Does “guix build” not respect these build properties?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-05-31 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  4:11 bug#27157: Building Guile 2.2 "times out" Maxim Cournoyer
2017-05-31 11:44 ` Ricardo Wurmus [this message]
2017-05-31 21:01   ` Ludovic Courtès
2017-06-01 16:06     ` Maxim Cournoyer
2017-06-01 21:37       ` Ludovic Courtès
2017-06-03 20:38         ` bug#27157: [PATCH] " Maxim Cournoyer
2017-06-03 21:37           ` Ludovic Courtès
2017-06-03 23:09             ` Maxim Cournoyer
2017-06-04 13:26               ` Ludovic Courtès
2017-08-31 13:19         ` Maxim Cournoyer
2017-09-01  9:10           ` Ludovic Courtès
2017-06-03  0:57   ` Mark H Weaver
2017-06-03  7:48     ` Ricardo Wurmus
2017-06-07 23:17       ` Mark H Weaver
2017-06-07 23:35         ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tld2quh.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=27157@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).