From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 324] eal/cmdline_autotest failed
Date: Wed, 17 Jul 2019 06:15:57 +0000 [thread overview]
Message-ID: <bug-324-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=324
Bug ID: 324
Summary: eal/cmdline_autotest failed
Product: DPDK
Version: 19.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: wenjiex.a.li@intel.com
Target Milestone: ---
After compile dpdk with gcc and bind the NIC ports, run below commands:
./x86_64-native-linuxapp-gcc/app/test -n 1 -c 0xff
testpmd> cmdline_autotest
The output is:
Testind parsing ethernet addresses...
Error: parsing 01:23:45:67:89:A succeeded!
Test Failed
Expeted Result:
Testind parsing ethernet addresses...
Testind parsing port lists...
Testind parsing numbers...
Testing parsing IP addresses...
Testing parsing strings...
Testing circular buffer...
Testing library functions...
Test OK
The 1st bad commit id is:
6efc06725fade989675b5051b6e5a623473d0894
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri Jul 5 10:16:20 2019 -0700
cmdline: use new ethernet address parser
Now that there is a version of ether_aton in rte_ether, it can
be used by the cmdline ethernet address parser.
Note: ether_aton_r can not be used in cmdline because
the old code would accept either bytes XX:XX:XX:XX:XX:XX
or words XXXX:XXXX:XXXX and we need to keep compatibility.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-07-17 6:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-324-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.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).