From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Skipping tests during install/build
Date: Sun, 12 Feb 2017 14:30:01 +0100 [thread overview]
Message-ID: <877f4vy1t2.fsf@gnu.org> (raw)
In-Reply-To: <87tw807ed2.fsf@gnu.org> (Mike Gerwitz's message of "Sat, 11 Feb 2017 13:48:41 -0500")
Hi Mike,
Mike Gerwitz <mtg@gnu.org> skribis:
> Is there a way (without screwing anything up) to skip tests during a
> build? I understand that this is generally unwise---I don't want to
> debate those merits.
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 think it’s a feature, though. :-)
> My immediate problem is that I'm on a dinky little ARM C201 Chromebook
> and any sort of building is quite time-consuming, and often
> prohibitively so: I can deal with the compilation times, but the tests
> are simply too much; I don't have time to wait potentially hours for
> software to build if they aren't available from hydra. GnuTLS is one
> particularly intense dependency test-wise, for example. And then if a
> test fails for whatever reason, I'm completely out of luck. I'd rather
> install and then run tests later at my leisure, accepting the risks.
>
> But I don't know if any test output is taken into account in any Guix
> hashes.
>
> There are a few situations where I've had no choice but to fall back to
> installing the respective Debian package(s). But I've been very
> impressed with how many ARM packages _are_ available from hydra---many
> more than I had expected!
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.
Part of it is due to the fact that they have fewer build machines¹ so
they tend to lag behind. The second problem is that they have fewer
users; developers don’t always notice when something breaks there and
cannot fix issues easily if they don’t have access to the hardware.
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.
Thanks,
Ludo’.
¹ See the list at <https://www.gnu.org/software/guix/donate/>.
next prev parent reply other threads:[~2017-02-12 13:30 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 [this message]
2017-02-12 23:55 ` Mike Gerwitz
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=877f4vy1t2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mtg@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).