unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: prefetch tarballs in a batch
Date: Tue, 06 May 2014 22:02:24 +0200	[thread overview]
Message-ID: <87r4461xrj.fsf@gnu.org> (raw)
In-Reply-To: <87r447t75q.fsf@karetnikov.org> (Nikita Karetnikov's message of "Tue, 06 May 2014 16:37:21 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> 1. It doesn’t seem to prefetch all the needed dependencies.  ‘guix build
>    hello’ (without network access) fails after prefetching the said
>    package.

Fails how?

> 2. The substituter fails from time to time.  Note that eight tests fail
>    on the machine I used: ‘builders.scm’, ‘utils.scm’, ‘packages.scm’,
>    ‘store.scm’, ‘monads.scm’, ‘gexp.scm’, ‘guix-package.sh’,
>    ‘guix-register.sh’.  Perhaps we ought to fix the mentioned failures
>    first.  Which log files would you like to see?

The SRFI-64 log files of the failing tests, plus test-suite.log.  Test
failures must not remain uncorrected!  ;-)

When there are so many failures, it’s likely that there’s a setup issue,
like socket names are too long.

>    $ ./pre-inst-env guix prefetch -n icecat
>    substitute-binary: guile: hashtab.c:137: vacuum_weak_hash_table: Assertion `removed <= len' failed.

What Guile and libgc version is this, and what platform?

>    I’ve also seen this one.  In case it matters, that was before running
>    ‘chgrp 1001 /gnu/store; chmod 1775 /gnu/store’.
>
>    $ ./pre-inst-env guix prefetch -n gnunet
>    Backtrace:
>    In ice-9/boot-9.scm:
>     157: 17 [catch #t #<catch-closure 9319ef0> ...]

[...]

>    In guix/derivations.scm:
>     175: 3 [derivation-prerequisites-to-build # # # ...]
>    In guix/store.scm:
>     695: 2 [substitutable-paths # #]
>     392: 1 [process-stderr #<build-daemon 256.14 9a29660> #f]
>    In guix/serialization.scm:
>      51: 0 [read-int #<input-output: socket 11>]
>
>    guix/serialization.scm:51:4: In procedure read-int:
>    guix/serialization.scm:51:4: In procedure bv-u32-ref: Wrong type argument in position 1 (expecting bytevector): #<eof>

That seems similar no?

Does the installation seem sane, basically?  Do ‘guix build’, ‘guix
package’ etc. work somehow, or not even?

> 3. When using the substituter, the command takes much more time.  Do
>    we even need it in this case?  I seem to recall that the GNUnet
>    tarball was served by Hydra, but I forgot the details.

There’s a local cache of substituter hits/failures in
/var/guix/substitute-binary (or similar.)  When that cache is empty or
outdated, a lot of HTTP queries are made to hydra.gnu.org, which can
take a bit of time.

When using a recent Guile, these queries are made in parallel.  On my
machine, it goes like this:

--8<---------------cut here---------------start------------->8---
$ sudo rm -rf /var/guix/substitute-binary/cache/

$ time guix build emacs -n

real	0m30.551s
user	0m2.519s
sys	0m0.154s

$ time guix build emacs -n

real	0m3.381s
user	0m2.039s
sys	0m0.123s
--8<---------------cut here---------------end--------------->8---

The cost is high when starting from an empty cache, but afterwards it’s
small.

> +(define (show-help)

Add call to ‘show-build-options-help’ from (guix scripts build).

> +(define %options
> +  ;; Specification of the command-line options.
> +  (list (option '("no-substitutes") #f #f
> +                (lambda (opt name arg result . rest)
> +                  (apply values
> +                         (alist-cons 'substitutes? #f
> +                                     (alist-delete 'substitutes? result))
> +                         rest)))

Remove this option, and concatenate with ‘%standard-build-options’.

> +                       (filter-map (match-lambda
> +                                    (('argument . value)
> +                                     (identity  ; discard the second value

The extra value gets truncated here, so it’s not strictly needed.

Thanks!

Ludo’.

  reply	other threads:[~2014-05-06 20:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 23:25 Proposal: prefetch tarballs in a batch Nikita Karetnikov
2014-03-28 13:23 ` Ludovic Courtès
2014-04-01 23:23   ` Nikita Karetnikov
2014-04-02 12:57     ` Ludovic Courtès
2014-04-02 22:37       ` Nikita Karetnikov
2014-04-03  7:24         ` Ludovic Courtès
2014-04-09 22:29           ` Nikita Karetnikov
2014-04-10  8:21             ` Ludovic Courtès
2014-04-12 20:19               ` Nikita Karetnikov
2014-04-12 22:44                 ` Ludovic Courtès
2014-04-24 21:20                   ` Nikita Karetnikov
2014-04-25 11:51                     ` Ludovic Courtès
2014-04-25 12:04                     ` Ludovic Courtès
2014-05-06 12:37                       ` Nikita Karetnikov
2014-05-06 20:02                         ` Ludovic Courtès [this message]
2014-05-07 23:14                           ` Nikita Karetnikov
2014-05-08 16:35                             ` Ludovic Courtès
2014-05-11 14:52                               ` Nikita Karetnikov
2014-05-11 19:17                                 ` Ludovic Courtès
2014-09-02 21:06                                   ` Ludovic Courtès
2014-09-02 22:05                                     ` Nikita Karetnikov
2014-09-02 21:04                               ` Ludovic Courtès

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=87r4461xrj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=nikita@karetnikov.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 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).