From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: bug#21410: [TEST-FAIL] 2 tests failed when running `make check' on Debian Date: Sun, 6 Sep 2015 07:25:44 -0400 Message-ID: References: <20150906123025.64b32157@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52265) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZYY5F-0005Zz-4x for bug-guix@gnu.org; Sun, 06 Sep 2015 07:26:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZYY5C-0004kp-0k for bug-guix@gnu.org; Sun, 06 Sep 2015 07:26:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58298) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZYY5B-0004ka-Tc for bug-guix@gnu.org; Sun, 06 Sep 2015 07:26:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZYY5B-00077M-Pw for bug-guix@gnu.org; Sun, 06 Sep 2015 07:26:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20150906123025.64b32157@debian> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Alex Vong Cc: 21410@debbugs.gnu.org [ re-CCing Ludo and bug-guix ] On Sun, Sep 6, 2015 at 12:30 AM, Alex Vong wrote: > Hi Dave, > > 2015-09-06 1:43 GMT+08:00, Thompson, David : >> >> 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