all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia@riseup.net
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Error log analys from building ~2851 packages
Date: Fri, 08 Jan 2016 19:01:44 +0100	[thread overview]
Message-ID: <87oacwdk6v.fsf@gnu.org> (raw)
In-Reply-To: <df65c63620c37167c47ab74e96e52624@riseup.net> (swedebugia@riseup.net's message of "Fri, 08 Jan 2016 18:18:47 +0100")

swedebugia@riseup.net skribis:

> Get the package list:
> guix package -A|pick the first field with cut/gawk >list
>
> Then a bash for-loop along the lines of:
> for $i in `cat list` ; echo "building $i" && do guix build $i
> --verbosity=1 -c 2 1<&2 build.log ; done
>
> Then follow the build with:
> tail -F build.log

OK.

>> I would like to provide a more convenient interface, like
>> ‘guix build --all’ or something like that.
>
> Sounds like a good idea. I would prefer if guix build to be able to
> instruct the daemon to cache failures if possible.

The default is to not cache failures, on the grounds that we experience
non-deterministic failures occasionally.  But I think we might want to
change the default at some point, since it’s always possible to clear
cached failures anyway.

Besides, on GuixSD, it’s always possible to change the options passed to
guix-daemon (info "(guix) Using the Configuration System"):

   (modify-services %base-services
     (guix-service-type config =>
                        (guix-configuration
                         (inherit config)
                         (extra-options '("--cache-failures")))))

Thanks,
Ludo’.

      reply	other threads:[~2016-01-08 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 18:22 Minimum requirements for building everything on GuixSD? swedebugia
2015-12-30 21:18 ` Ludovic Courtès
2015-12-31  1:22   ` Leo Famulari
2016-01-06 19:52     ` Error log analys from building ~2851 packages swedebugia
2016-01-07  8:53       ` Ricardo Wurmus
2016-01-07 14:33       ` Ludovic Courtès
2016-01-08 17:18         ` swedebugia
2016-01-08 18:01           ` Ludovic Courtès [this message]

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

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

  git send-email \
    --in-reply-to=87oacwdk6v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.