From: Cyprien Nicolas <cyprien@nicolas.tf>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 15052@debbugs.gnu.org
Subject: bug#15052: guix-0.3 make check fails, on gentoo-prefix setup
Date: Thu, 29 Aug 2013 23:56:38 +0200 [thread overview]
Message-ID: <20130829215638.GF2051@kubera.unice.fr> (raw)
In-Reply-To: <87y583gp8j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hello,
Il y a 14 jours, Ludovic Courtès écrivit :
> Hi!
>
> Cyprien Nicolas <cyprien@nicolas.tf> skribis:
>
> > I don't understand all failures, some are due to socket path length:
> >
> > ERROR: In procedure connect:
> > ERROR: In procedure scm_to_sockaddr: unix address path too long: /home/cnicolas/gprefix/var/tmp/portage/sys-apps/guix-0.3/work/guix-0.3/test-tmp/var/7770/daemon-socket/socket
>
> Apff, yes, that’s a problem. Guix clients connect to the build daemon
> over a Unix-domain socket, and that has a shameful 108 character limit
> on GNU/Linux. Thus, all the test cases that try to connect to the build
> daemon fail.
>
> As a workaround, you could try to build in a shorter directory, if
> that’s an option at all.
Yes, I exported PORTAGE_TMPDIR=/tmp before running emerge, and all 19
tests went fine :-)
> Alternately, you could try changing the ‘test-env’ script to use
> relative directory names instead.
I haven't try it. No real opinion on which one would be prefered.
> Can you try and report back?
Done!
--
Cyprien/Fulax
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-08-29 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 21:30 bug#15052: guix-0.3 make check fails, on gentoo-prefix setup Cyprien Nicolas
2013-08-15 11:36 ` Ludovic Courtès
2013-08-29 21:56 ` Cyprien Nicolas [this message]
2013-08-30 9: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
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=20130829215638.GF2051@kubera.unice.fr \
--to=cyprien@nicolas.tf \
--cc=15052@debbugs.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.
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).