From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] Recent failure in autotest
Date: Tue, 22 Sep 2020 16:11:22 -0700 [thread overview]
Message-ID: <20200922161122.052225c1@hermes.lan> (raw)
The blacklist/whitelist documentation patch which is totally unrelated to this failed
in the unit test. Looks like recent cmdline changes caused a problem?
10: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x3973a) [0x55acef45573a]]
9: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1389384b97]]
8: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x3882d) [0x55acef45482d]]
7: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(cmdline_in+0x79) [0x7f138e69aac9]]
6: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(rdline_char_in+0x6a8) [0x7f138e69e2d8]]
5: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(+0x29f0) [0x7f138e69a9f0]]
4: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(cmdline_parse+0x328) [0x7f138e69ba08]]
3: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x39853) [0x55acef455853]]
2: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0xac593) [0x55acef4c8593]]
1: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_eal.so.21(rte_dump_stack+0x2e) [0x7f13907e79ae]]
PANIC in test_panic():
Test Debug
next reply other threads:[~2020-09-22 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 23:11 Stephen Hemminger [this message]
2020-09-23 7:45 ` David Marchand
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=20200922161122.052225c1@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).