From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: autotest system requirements.
Date: Wed, 20 Jul 2022 12:07:59 +0100 [thread overview]
Message-ID: <YtfiD2jrclprZaHg@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220719130007.629262e4@hermes.local>
On Tue, Jul 19, 2022 at 01:00:07PM -0700, Stephen Hemminger wrote:
> With 22.07 release, the test requirements seemed to have changed.
> Can't run tests unless root now.
>
> And the table test fails if only 1G of hugepages is setup.
>
> This doesn't match the documentation:
> https://doc.dpdk.org/guides/prog_guide/meson_ut.html
>
> which shows running tests as non-root.
Can you clarify a bit more what you are seeing? I can certainly run a suite
of unit tests as non-root and have the majority of them pass. There are
failures and timeouts though, but I haven't root-caused why exactly.
/Bruce
$ meson test --suite DPDK:fast-tests
ninja: Entering directory `/home/bruce/dpdk.org/build'
ninja: no work to do.
1/102 DPDK:fast-tests / acl_autotest OK 3.05s
2/102 DPDK:fast-tests / atomic_autotest TIMEOUT 10.01s killed by signal 15 SIGTERM
>>> DPDK_TEST=atomic_autotest MALLOC_PERTURB_=252 /home/bruce/dpdk.org/build/app/test/dpdk-test --file-prefix=atomic_autotest
[3/102] ð 3/102 DPDK:fast-tests / bitmap_autotest OK 0.14s
4/102 DPDK:fast-tests / bpf_autotest OK 0.12s
5/102 DPDK:fast-tests / bpf_convert_autotest OK 0.14s
...
100/102 DPDK:fast-tests / pdump_autotest OK 5.46s
101/102 DPDK:fast-tests / vdev_autotest OK 0.16s
102/102 DPDK:fast-tests / compressdev_autotest SKIP 0.15s exit status 77
Ok: 88
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 5
Timeout: 8
Full log written to /home/bruce/dpdk.org/build/meson-logs/testlog.txt
next prev parent reply other threads:[~2022-07-20 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 20:00 Stephen Hemminger
2022-07-20 11:07 ` Bruce Richardson [this message]
2022-07-20 15:42 ` Stephen Hemminger
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=YtfiD2jrclprZaHg@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).