util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: util-linux@vger.kernel.org
Subject: An obscure problem with v2.37 make check
Date: Wed, 16 Jun 2021 15:42:04 -0500	[thread overview]
Message-ID: <cdfa712c-c918-c5bd-e320-b3dbe8599bbd@gmail.com> (raw)

When I built version v2.37, make check hung on me.  The problem was in 
my kernel configuration, but I thought I would pass this on.

First of all, my biggest problem was finding out what had failed.  A 
simple 'make check' ran the tests and when it got to the end, hung.

I could not find any documentation about running the tests, but diving 
into the Makefile led me to tests/run.sh.  By default this runs tests 
using all cores, but it is unclear if this is meant to be run directly.

In any case running run.sh --parallel=1 (instead of the default 24) 
allowed me to find the problem test, tests/ts/lsns/ioctl_ns.  In this 
test, it is doing:

my_userns=$(stat -c %i -L /proc/self/ns/user)

My problem was that /proc/self/ns/user did not exist on my system.  This 
was due to a missing CONFIG option in my kernel configuration.  Adding 
that and rebuilding the kernel allowed all tests to pass.

One solution to this problem may be to test for the existence of the 
file before running 'stat' similar to the tests for programs like 
'touch' and 'uniq'.  Since this is such an unusual situation, I can 
understand if you just ignore the issue, however I thought you should 
know about it.

   -- Bruce

             reply	other threads:[~2021-06-16 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 20:42 Bruce Dubbs [this message]
2021-06-17  8:59 ` An obscure problem with v2.37 make check Karel Zak
2021-06-17 12:37   ` Anatoly Pugachev
2021-06-17 16:50     ` Bruce Dubbs
2021-06-18 12:47       ` Karel Zak

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cdfa712c-c918-c5bd-e320-b3dbe8599bbd@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=util-linux@vger.kernel.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.
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 NNTP newsgroup(s).