From: ludo@gnu.org (Ludovic Courtès)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Test suite failures
Date: Mon, 13 Jul 2015 18:45:46 +0200 [thread overview]
Message-ID: <87pp3wypj9.fsf_-_@gnu.org> (raw)
In-Reply-To: <dbf9343635144f20888de6df35434630@exchsrv2.sgc.loc> (Malcolm Cook's message of "Sat, 11 Jul 2015 00:48:51 +0000")
(Stripping the list of recipients.)
"Cook, Malcolm" <MEC@stowers.org> skribis:
> In that thread, you suggested "What about installing Guix in /gnu/bin (say) and sharing it over NFS?". Is there a way to `./bootstrap ./configure ` this? Something like -- exec_prefix=/gnu --localstatedir=/gnu/var?
Yes, --exec-prefix=/gnu --localstatedir=/gnu/var (note “--exec-prefix”
with a hyphen.)
> Also, you discussed need for setting NIX_STATE_DIR. This should not be needed if guix was already installed with configuration of --localstatedir=/guix/var (with /guix being nfs mounted), right?
Right.
> Ricardo also wrote "For ‘guix package’ to work, /gnu/var/guix/profiles/per-user must be shared read-write (over NFS) with correct UID mapping." - I really don't understand this and tried to elicit feedback in http://lists.nongnu.org/archive/html/guix-devel/2015-07/msg00216.html - Can anyone give me clarification on this. I though the guix daemon is going to manage these profiles.
‘guix package’ makes remote procedure calls (RPCs) to the daemon and the
daemon does most things on its behalf.
However, there’s one thing that ‘guix package’ does directly by itself:
updating the profile symlinks, ~/.guix-profile and its target, which is
in $localstatedir.
For that reason, ‘guix package’ must have write access to
$localstatedir.
Does that clarify things?
> ============================================================================
> Testsuite summary for GNU Guix 0.8.3
> ============================================================================
> # TOTAL: 42
> # PASS: 32
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 10
> # XPASS: 0
> # ERROR: 0
[...]
> FAIL: tests/cpio.scm
What does ‘cpio --version’ returns? Could you email me (privately) the
file ‘t.cpio’ made with these commands:
cd /path/to/guix
ln -s chbouib /tmp/somelink
(for i in / $PWD /tmp/somelink $PWD/guix.scm \
$PWD/guix/build/syscalls.scm $PWD/guix/packages.scm ; \
do echo $i ; done ) | \
cpio -o -O t.cpio -H newc
> FAIL: tests/builders.scm
> FAIL: tests/derivations.scm
These two show errors like:
--8<---------------cut here---------------start------------->8---
output path `/home/mec/project/sce/guix/test-tmp/store/2l1h7am3q3c6sd4z5425mp3kjady6nla-hello-2.8.tar.gz should be a non-executable regular file
--8<---------------cut here---------------end--------------->8---
Which makes it sound like files are automatically made executable on
this file system.
What does ‘umask’ return?
What about ‘mount | grep /home’?
> FAIL: tests/packages.scm
Ditto.
> PASS: tests/snix.scm
> PASS: tests/hackage.scm
> PASS: tests/elpa.scm
> FAIL: tests/store.scm
This one shows this:
--8<---------------cut here---------------start------------->8---
;;; (c #<condition &nix-protocol-error [message: "path `/home/mec/project/sce/guix/test-tmp/stor?/vlryjv621i7xj4sr8ajzl9k9w5bmkv5c-text' is not in the Nix store" status: 1] 24a61e0>)
tests/store.scm:560: FAIL import corrupt path
;;; (verify1 #t)
;;; (verify2 #f)
;;; (verify3 #t)
tests/store.scm:620: FAIL verify-store + check-contents
--8<---------------cut here---------------end--------------->8---
This particular test is not designed to work with long $top_builddir
like this (the test corrupts an archive, but in this case the corruption
occurs in the middle of the file name, which confuses the test logic.)
I’ll see how to fix it.
> FAIL: tests/nar.scm
--8<---------------cut here---------------start------------->8---
tests/nar.scm:172: FAIL write-file puts file in C locale collation order
--8<---------------cut here---------------end--------------->8---
> FAIL: tests/union.scm
“Non-executable” error as before.
> PASS: tests/profiles.scm
> FAIL: tests/syscalls.scm
Harmless clone/setns/pivot-root test failures probably due to the fact
that the host kernel is too old. Can you confirm that this is fixed in
‘master’ (commit b62a3eb)? Simply run:
make check TESTS=tests/syscalls.scm
> FAIL: tests/guix-package-net.sh
“Non-executable” error again.
> FAIL: tests/guix-environment.sh
Likewise.
Thanks for your help!
Ludo’.
next prev parent reply other threads:[~2015-07-13 16:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 20:22 Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-06-19 8:06 ` Ricardo Wurmus
2015-06-19 11:34 ` Ludovic Courtès
2015-06-25 6:40 ` Ricardo Wurmus
2015-06-19 11:40 ` Ludovic Courtès
2015-07-08 19:20 ` Cook, Malcolm
2015-07-08 19:43 ` Ricardo Wurmus
2015-06-19 17:48 ` Cook, Malcolm
2015-06-24 19:57 ` Ludovic Courtès
2015-07-08 18:03 ` Cook, Malcolm
2015-07-08 19:53 ` Ricardo Wurmus
2015-07-10 8:39 ` Ludovic Courtès
2015-07-11 0:48 ` Cook, Malcolm
2015-07-13 16:45 ` Ludovic Courtès [this message]
2015-07-18 3:04 ` Test suite failures Cook, Malcolm
2015-07-18 15:02 ` Ludovic Courtès
2015-07-11 0:54 ` Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-07-15 15:45 ` Ricardo Wurmus
2015-07-15 19:49 ` Cook, Malcolm
2015-07-15 20:28 ` Pjotr Prins
2015-07-18 9:26 ` Cook, Malcolm
2015-07-18 15:13 ` Ludovic Courtès
2015-07-19 9:18 ` Claes Wallin (韋嘉誠)
2015-07-19 9:33 ` Andreas Enge
2015-07-20 22:37 ` Cook, Malcolm
2015-07-21 20:23 ` Cook, Malcolm
2015-07-21 20:29 ` Ricardo Wurmus
2015-07-23 22:52 ` Ludovic Courtès
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=87pp3wypj9.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=MEC@stowers.org \
--cc=guix-devel@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.
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.