From: Mike Gerwitz <mtg@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Skipping tests during install/build
Date: Sun, 12 Feb 2017 18:55:37 -0500 [thread overview]
Message-ID: <87poin3qx2.fsf@gnu.org> (raw)
In-Reply-To: <877f4vy1t2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 12 Feb 2017 14:30:01 +0100")
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Sun, Feb 12, 2017 at 14:30:01 +0100, Ludovic Courtès wrote:
> The short answer is “no”. The Boolean that determines whether tests are
> run is an “input” of the build process, and thus it contributes to that
> /gnu/store hash. Changing it leads to a different hash.
I was hoping for a `guix package -i --dont-do-this` kind of flag, not
changing the inputs.
> I think it’s a feature, though. :-)
It is. I'm just looking to selfishly subvert your good intentions. :)
> The intent is to have as much as possible available as substitutes.
> However, while this works well for x86_64, the other platforms are not
> in as good a state.
Oh, I want to be clear that I don't have a problem with the state of ARM
substitutes in itself; like I said, I'm surprised there are as many as
there are.
> So I think it’s a chicken-and-egg problem. Reporting the problems that
> you have on ARM (test suite failures, build failures, etc.) can help
> raise awareness and get people to fix things more quickly.
Yep, will do.
Thanks.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
Old: 2217 5B02 E626 BC98 D7C0 C2E5 F22B B815 8EE3 0EAB
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2017-02-12 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 18:48 Skipping tests during install/build Mike Gerwitz
2017-02-12 13:30 ` Ludovic Courtès
2017-02-12 23:55 ` Mike Gerwitz [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=87poin3qx2.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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.
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).