From: "Thompson, David" <dthompson2@worcester.edu>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 21410@debbugs.gnu.org
Subject: bug#21410: [TEST-FAIL] 2 tests failed when running `make check' on Debian
Date: Sun, 6 Sep 2015 07:25:44 -0400 [thread overview]
Message-ID: <CAJ=Rwfa9pWamLkgAX6iKUPPpkDiCxJcPxAdzWOWZSeCovT-M3A@mail.gmail.com> (raw)
In-Reply-To: <20150906123025.64b32157@debian>
[ re-CCing Ludo and bug-guix ]
On Sun, Sep 6, 2015 at 12:30 AM, Alex Vong <alexvong1995@gmail.com> wrote:
> Hi Dave,
>
> 2015-09-06 1:43 GMT+08:00, Thompson, David <dthompson2@worcester.edu>:
>>
>> Fixed in cf897cb.
>>
>> Alex, could you pull the master branch, run the tests, and send the
>> new log files?
>>
>> Thanks!
>>
>> - Dave
>>
>
> Sure, they are in the attachment.
>
> The build is done using fresh git-clone.
Thanks. So, the issue is that the clone(2) system call is failing
with the EPERM error code, meaning the operation is not permitted.
This is odd because all users are allowed to call 'clone' with the
CLONE_NEWUSER flag to create a process in a new user namespace.
However, the clone(2) man page specifies a couple of cases in which
this can fail:
EPERM CLONE_NEWUSER was specified in flags, but either the effective
user ID or the effective group ID of the caller does not have a
mapping in the parent namespace (see user_namespaces(7)).
EPERM (since Linux 3.9)
CLONE_NEWUSER was specified in flags and the caller is in a
chroot environment (i.e., the caller's root directory does not
match the root directory of the mount namespace in which it
resides).
Do any of these apply to you? Are you in a chroot or otherwise
virtualized environment? Anything else you can think of that could
cause this error would be appreciated.
Thanks,
- Dave
next parent reply other threads:[~2015-09-06 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150906123025.64b32157@debian>
2015-09-06 11:25 ` Thompson, David [this message]
2015-09-04 6:44 bug#21410: [TEST-FAIL] 2 tests failed when running `make check' on Debian Alex Vong
2015-09-04 14:12 ` Thompson, David
2015-09-04 15:02 ` Alex Vong
2015-09-04 20:07 ` Ludovic Courtès
2015-09-05 12:49 ` Thompson, David
2015-09-05 17:43 ` Thompson, David
2015-09-07 1:47 ` Alex Vong
2015-09-07 19:42 ` Thompson, David
2015-09-09 10:02 ` Alex Vong
2015-09-15 11:24 ` Alex Vong
2015-09-15 14:20 ` Thompson, David
2015-09-15 15:06 ` Alex Vong
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='CAJ=Rwfa9pWamLkgAX6iKUPPpkDiCxJcPxAdzWOWZSeCovT-M3A@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=21410@debbugs.gnu.org \
--cc=alexvong1995@gmail.com \
/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).