unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix build--rounds=N does not behave as expected
Date: Mon, 31 Dec 2018 18:23:56 +0100	[thread overview]
Message-ID: <ced54891-ff15-03a7-2fcc-85b07751e556@riseup.net> (raw)
In-Reply-To: <87pnthg9ti.fsf@elephly.net>

On 2018-12-31 13:27, Ricardo Wurmus wrote:
> 
> Hi swedebugia,
> 
> “guix build --rounds=N” builds the package N times if it hasn’t already
> been built.  With grafts enabled this would be the graft derivation,
> which isn’t very useful.
> 
> If the package has previously been built, however, it won’t rebuild the
> package.  That’s why we have “--check”.
> 
>> I really think we should signal a helpful error to the user if only
>> --rounds=N is specified and --check is missing.
> 
> Using “--rounds” without “--check” is correct.  There should not be an
> error or a warning in that case.

Rounds does not seem to work.
E.g. I ran this:
$ guix build automake --check --rounds=2

and the result was this:
phase `compress-documentation' succeeded after 0.1 seconds
/gnu/store/k7gymsw2xfp20fv30x5niilwnxpj2d2k-automake-1.16.1

I think this is a bug.
Rounds should ignore the item in store and swallow check so that it does 
what the user expects.

Right now it seems that check swallows rounds and rounds alone fail 
because the item is already in the store.

Alternatively I would like that guix ask me if I want to build the 
rounds EVEN THOUGH it is in the store. But that would be less nice.

-- 
Cheers Swedebugia

      parent reply	other threads:[~2018-12-31 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31 10:39 guix build--rounds=N does not behave as expected swedebugia
2018-12-31 12:27 ` Ricardo Wurmus
2018-12-31 16:52   ` Arun Isaac
2018-12-31 17:23   ` swedebugia [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

  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=ced54891-ff15-03a7-2fcc-85b07751e556@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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 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).