From: Alex Vong <alexvong1995@gmail.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: 21410@debbugs.gnu.org
Subject: bug#21410: [TEST-FAIL] 2 tests failed when running `make check' on Debian
Date: Wed, 9 Sep 2015 18:02:57 +0800 [thread overview]
Message-ID: <CADrxHD_GVXXvyfszexbAW2H8OEa-wV_eXPkQvSA-rpBEufkLeQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ=RwfZH1Mc+KCW4-_GmpDQ8LP3AV0wki5SxmoVTbCKFWOa3mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]
Hi Dave,
It appears that the patch doesn't quite work, now 20 tests failed
instead of 2. The log files are attached as a tar ball. I have tried
running the tests on the old source as well as on fresh new git clone.
In any case, 20 tests failed. I wonder why this happens.
Cheers,
Alex
2015-09-08 3:42 GMT+08:00, Thompson, David <dthompson2@worcester.edu>:
> On Sun, Sep 6, 2015 at 9:47 PM, Alex Vong <alexvong1995@gmail.com> wrote:
>> Hi Dave,
>>
>> I have searched the internet according to the information you provided,
>> I find this bug report <https://github.com/lxc/lxc/issues/250> provides
>> useful information.
>> I have written an example program after going through the clone(2) man
>> page.
>> It demonstrates the problem and is inlined below.
>>
>> First, compile the program as `a.out'.
>>
>> Consider shell session 1:
>>
>> root# echo 0 > /proc/sys/kernel/unprivileged_userns_clone
>> user$ ./a.out
>> I am your parent
>> Start cloning...
>> Cannot clone!
>>
>> Consider shell session 2:
>>
>> root# echo 1 > /proc/sys/kernel/unprivileged_userns_clone
>> user$ ./a.out
>> I am your parent
>> Start cloning...
>> Cloned!
>> I am your child
>>
>> Any idea what's happenning?
>> I don't know Linux much, for instance I don't know what is container and
>> namespace in Linux.
>
> It seems that the kernel you are using has disabled the use of
> unprivileged user namespaces by default. After doing that echo as
> root, you should be able to run the tests successfully. Could you
> apply the attached patch and let me know if 'make check
> TESTS=tests/syscalls.scm' and 'make check TESTS=tests/containers.scm'
> pass in both when unprivileged user namespaces are disabled and when
> they are enabled?
>
> Thank you!
>
> - Dave
>
[-- Attachment #2: guix.tar.xz --]
[-- Type: application/x-xz, Size: 129272 bytes --]
next prev parent reply other threads:[~2015-09-09 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-09-15 11:24 ` Alex Vong
2015-09-15 14:20 ` Thompson, David
2015-09-15 15:06 ` Alex Vong
[not found] <20150906123025.64b32157@debian>
2015-09-06 11:25 ` Thompson, David
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=CADrxHD_GVXXvyfszexbAW2H8OEa-wV_eXPkQvSA-rpBEufkLeQ@mail.gmail.com \
--to=alexvong1995@gmail.com \
--cc=21410@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
/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).