From: "Michal Suchánek" <msuchanek@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NVDIMM <nvdimm@lists.linux.dev>
Subject: Re: ndctl tests usable?
Date: Tue, 26 Apr 2022 18:14:35 +0200 [thread overview]
Message-ID: <20220426161435.GH163591@kunlun.suse.cz> (raw)
In-Reply-To: <CAPcyv4j66HAE_x-eAHQR71pNyR0mk5b463S6OfeokLzZHq5ezw@mail.gmail.com>
On Tue, Apr 26, 2022 at 08:51:25AM -0700, Dan Williams wrote:
> On Tue, Apr 26, 2022 at 5:39 AM Michal Suchánek <msuchanek@suse.de> wrote:
> >
> > Hello,
> >
> > there is some testsuite included with ndctl, and when following the
> > instructions to build it most tests fail or are skipped:
> >
> > [ 95s] Ok: 3
> > [ 95s] Expected Fail: 0
> > [ 95s] Fail: 5
> > [ 95s] Unexpected Pass: 0
> > [ 95s] Skipped: 15
> > [ 95s] Timeout: 0
> >
> > Is this the expected outcome or is this a problem with the ndctl build?
> >
> > Attaching test run log.
>
> I see a few missing prerequisites:
>
> [ 78s] /usr/src/packages/BUILD/ndctl-73/test/pmem-errors.sh: line
> 64: mkfs.ext4: command not found
> [ 95s] /usr/src/packages/BUILD/ndctl-73/test/security.sh: line 25:
> jq: command not found
Indeed, with those installed I get much more tests passing:
[ 148s] Ok: 13
[ 148s] Expected Fail: 0
[ 148s] Fail: 4
[ 148s] Unexpected Pass: 0
[ 148s] Skipped: 6
[ 148s] Timeout: 0
>
> This report:
>
> [ 51s] 1/23 ndctl:ndctl / libndctl SKIP
> 0.02s exit status 77
>
> ...seems to indicate that the nfit_test modules did not appear to load
> correctly. I never expected that the nfit_test modules would be
> redistributable, so I was surprised to see them being installed by an
> actual package "nfit_test-kmp-default-0_k5.17.4_1-6.1". The reason
> they are not redistributable is because they require replacing the
> production build of the kernel provided modules libnvdimm.ko,
> nd_pmem.ko, etc... What I expect is happening is that the production
> version of libnvdimm.ko is already loaded (or is the only one on the
AFAICT neither is the case, that's why I dump the module information in
the log.
Thanks
Michal
next prev parent reply other threads:[~2022-04-26 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 12:38 Michal Suchánek
2022-04-26 15:51 ` Dan Williams
2022-04-26 16:14 ` Michal Suchánek [this message]
2022-04-26 16:32 ` Dan Williams
2022-04-26 16:38 ` Michal Suchánek
2022-04-26 16:47 ` Dan Williams
2022-04-26 18:09 ` Michal Suchánek
2022-04-26 18:22 ` Dan Williams
2022-04-27 11:26 ` Michal Suchánek
2022-04-28 4:32 ` Shivaprasad G Bhat
2022-04-28 8:51 ` Michal Suchánek
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=20220426161435.GH163591@kunlun.suse.cz \
--to=msuchanek@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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
all inboxes | Powered by JetHome®