From: Mike Gerwitz <mtg@gnu.org>
To: help-guix@gnu.org
Subject: Skipping tests during install/build
Date: Sat, 11 Feb 2017 13:48:41 -0500 [thread overview]
Message-ID: <87tw807ed2.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Hello, everyone:
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.
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!
Anyway: any suggestions? :/
--
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 --]
next reply other threads:[~2017-02-11 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 18:48 Mike Gerwitz [this message]
2017-02-12 13:30 ` Skipping tests during install/build Ludovic Courtès
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=87tw807ed2.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=help-guix@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).