(address . bug-guix@gnu.org)
CAKKYfmGsJABh6o3Yk9gkE_Kd3JSMKhj8633eZ-LFMsb3KZmYgw@mail.gmail.com
See attached test suite log.
Build used: latest master branch clone from git.
on 12 Dec 2015 11:00
on 13 Dec 2015 03:09
Make check fails
- Done
Details
- 2 participants
- Dennis Mungai
- Ludovic Courtès
- Owner
- unassigned
- Submitted by
- Dennis Mungai
- Severity
- normal
(name . Dennis Mungai)(address . dmngaie@gmail.com)(address . 22153@debbugs.gnu.org)
87oaduy58h.fsf@gnu.org
Hi,
Dennis Mungai <dmngaie@gmail.com> skribis:
Toggle quote (7 lines)
> + GUIX_DAEMON_SOCKET=/home/administrator/source.build/GCC.buildenv/guix-0.9.0/t-register-39139/var/guix/guix/daemon-socket/socket
> + export NIX_IGNORE_SYMLINK_STORE NIX_STORE_DIR NIX_STATE_DIR NIX_LOG_DIR NIX_DB_DIR GUIX_DAEMON_SOCKET
> ++ echo /home/administrator/source.build/GCC.buildenv/guix-0.9.0/t-register-39139/var/guix/guix/daemon-socket/socket
> ++ wc -c
> + '[' 109 -ge 108 ']'
> + exit 77
The build directory name is very long, which means that we are a likely
to hit the kernel’s limitation on the length of socket file names, as in
the snippet above.
What does this command:
grep ac_cv_guix_test_socket_file_name_length config.log
return?
At configure time, one normally gets a warning:
socket file name limit may be exceeded when running tests
(This is not an error because there’s no problem if you don’t run ‘make
check’.)
In your case I think you would have to build from a shorter directory.
HTH,
Ludo’.
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 22153@debbugs.gnu.org)
CAKKYfmFVU1+pZ3a6Ah-bk2gP74yFySeE9eK5eCcoBa_+5ZySoA@mail.gmail.com
Hello,
And sorry for replying so late.
A few days ago, I repeated the build under /tmp and all unit tests passed.
Could've been related to the issue above.
I'd have to repeat the guix build above in the same directory once I'm
logged on to the HPC's node to get you the requested results.
Regards,
Dennis.
On 13 December 2015 at 14:09, Ludovic Courtès <ludo@gnu.org> wrote:
Toggle quote (36 lines)
> Hi,
>
> Dennis Mungai <dmngaie@gmail.com> skribis:
>
> > +
> GUIX_DAEMON_SOCKET=/home/administrator/source.build/GCC.buildenv/guix-0.9.0/t-register-39139/var/guix/guix/daemon-socket/socket
> > + export NIX_IGNORE_SYMLINK_STORE NIX_STORE_DIR NIX_STATE_DIR
> NIX_LOG_DIR NIX_DB_DIR GUIX_DAEMON_SOCKET
> > ++ echo
> /home/administrator/source.build/GCC.buildenv/guix-0.9.0/t-register-39139/var/guix/guix/daemon-socket/socket
> > ++ wc -c
> > + '[' 109 -ge 108 ']'
> > + exit 77
>
> The build directory name is very long, which means that we are a likely
> to hit the kernel’s limitation on the length of socket file names, as in
> the snippet above.
>
> What does this command:
>
> grep ac_cv_guix_test_socket_file_name_length config.log
>
> return?
>
> At configure time, one normally gets a warning:
>
> socket file name limit may be exceeded when running tests
>
> (This is not an error because there’s no problem if you don’t run ‘make
> check’.)
>
> In your case I think you would have to build from a shorter directory.
>
> HTH,
> Ludo’.
>
(name . Dennis Mungai)(address . dmngaie@gmail.com)(address . 22153@debbugs.gnu.org)
871takivfn.fsf@gnu.org
Dennis Mungai <dmngaie@gmail.com> skribis:
Toggle quote (3 lines)
> A few days ago, I repeated the build under /tmp and all unit tests passed.
> Could've been related to the issue above.
Yes, probably.
Toggle quote (3 lines)
> I'd have to repeat the guix build above in the same directory once I'm
> logged on to the HPC's node to get you the requested results.
Sure.
Thanks for your feedback!
Ludo’.
control message for bug #22153
(address . control@debbugs.gnu.org)
87y4c6x6b7.fsf@gnu.org
tags 22153 notabug
(address . control@debbugs.gnu.org)
87wprqx6ay.fsf@gnu.org
close 22153 0.9.0
?