[PATCH] gnu: guile-next: Increase timeout.

[PATCH] gnu: guile-next: Increase timeout.

[Ricardo Wurmus]

* gnu/packages/guile.scm (guile-next)[properties]: Set timeout to
20 hours.
---
 gnu/packages/guile.scm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index 0890f19..7361f1f 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -220,6 +220,7 @@ without requiring the source code to be rewritten.")
               (snippet '(for-each delete-file
                                   (find-files "prebuilt" "\\.go$")))))
     (synopsis "Snapshot of what will become version 2.2 of GNU Guile")
+    (properties '((timeout . 72000)))  ; 20 hours
     (native-search-paths
      (list (search-path-specification
             (variable "GUILE_LOAD_PATH")
-- 
2.10.0

Re: [PATCH] gnu: guile-next: Increase timeout.

[Leo Famulari]

On Sat, Oct 08, 2016 at 10:00:44AM +0200, Ricardo Wurmus wrote:
> * gnu/packages/guile.scm (guile-next)[properties]: Set timeout to
> 20 hours.

Seems fine if that's how long it takes. Wow!

Re: [PATCH] gnu: guile-next: Increase timeout.

[Ricardo Wurmus]

Leo Famulari <leo@famulari.name> writes:

> On Sat, Oct 08, 2016 at 10:00:44AM +0200, Ricardo Wurmus wrote:
>> * gnu/packages/guile.scm (guile-next)[properties]: Set timeout to
>> 20 hours.
>
> Seems fine if that's how long it takes. Wow!

The comment above says that it takes in excess of three hours on
x86_64.  Considering that the build machines for other architectures are
less powerful and that they may be building more than one thing at a
time I think 20 hours is a very safe choice.  (Maybe a bit large, but
there’s no harm in that, I think.)

~~ Ricardo

Re: [PATCH] gnu: guile-next: Increase timeout.

[Andy Wingo]

On Sun 09 Oct 2016 08:43, Leo Famulari <leo@famulari.name> writes:

> On Sat, Oct 08, 2016 at 10:00:44AM +0200, Ricardo Wurmus wrote:
>> * gnu/packages/guile.scm (guile-next)[properties]: Set timeout to
>> 20 hours.
>
> Seems fine if that's how long it takes. Wow!

Yeah :/ Though with Ricardo's caveats that on an x86-64 machine it's
more like 2 or 3 hours.  This is "fixed" in the tarballs because the
person who generates the tarballs makes sure to prebuild a set of
compiled scheme files for common architectures, and those get picked up
by the build.  Otherwise yeah, slow, sorry about that :(

More background: https://wingolog.org/archives/2016/01/11/the-half-strap-self-hosting-and-guile

Andy