DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Recent failure in autotest
Date: Wed, 23 Sep 2020 09:45:23 +0200
Message-ID: <CAJFAV8yCWg9YXKBiKsoEq7dHGr3PjbTGzHL_d1j5+Dp9GuXbOw@mail.gmail.com> (raw)
In-Reply-To: <20200922161122.052225c1@hermes.lan>

On Wed, Sep 23, 2020 at 1:11 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> 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
>

This PANIC is usually expected... and is part of the check for rte_panic.
And looking at your series, the associated test passes fine (see below
for full trace).


On the other hand, your series breaks the unit test on the -w option.
This is why the CI (UNH and Travis) flagged your series.



10/92 DPDK:fast-tests / debug_autotest        OK       0.37 s

--- command ---
14:58:06 DPDK_TEST='debug_autotest'
/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test
-l 0-3 --file-prefix=debug_autotest
--- stdout ---
EAL: Probing VFIO support...
EAL: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
RTE>>debug_autotest
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
11: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x3973a)
[0x55acef45573a]]
10: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1389384b97]]
9: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x3882d)
[0x55acef45482d]]
8: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(cmdline_in+0x79)
[0x7f138e69aac9]]
7: [/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]]
6: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(+0x29f0)
[0x7f138e69a9f0]]
5: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_cmdline.so.21(cmdline_parse+0x328)
[0x7f138e69ba08]]
4: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0x39853)
[0x55acef455853]]
3: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test(+0xac763)
[0x55acef4c8763]]
2: [/home/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Unit-Test-DPDK/dpdk/build/app/test/../../lib/librte_eal.so.21(__rte_panic+0xc5)
[0x7f13907c5095]]
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]]
Child process terminated as expected - Test passed!
test_exit_valChild process terminated as expected - Test passed!
Child process status: 0
EAL: Error - exiting with code: 1
  Cause: test_exit_valChild process terminated as expected - Test passed!
Child process status: 0
Child process status: 256
EAL: Error - exiting with code: 2
  Cause: test_exit_valChild process terminated as expected - Test passed!
Child process status: 0
Child process status: 256
Child process status: 512
EAL: Error - exiting with code: 255
  Cause: test_exit_valChild process terminated as expected - Test passed!
Child process status: 0
Child process status: 256
Child process status: 512
Child process status: 65280
EAL: Error - exiting with code: -1
  Cause: test_exit_valChild process terminated as expected - Test passed!
Child process status: 0
Child process status: 256
Child process status: 512
Child process status: 65280
Child process status: 65280
test_exit Passed
Test OK
RTE>>
--- stderr ---
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /run/user/1002/dpdk/debug_autotest/mp_socket
EAL: Selected IOVA mode 'VA'
-------

11/92 DPDK:fast-tests / eal_flags_c_opt_autotest  OK       0.42 s


-- 
David Marchand


      reply	other threads:[~2020-09-23  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 23:11 Stephen Hemminger
2020-09-23  7:45 ` David Marchand [this message]

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=CAJFAV8yCWg9YXKBiKsoEq7dHGr3PjbTGzHL_d1j5+Dp9GuXbOw@mail.gmail.com \
    --to=david.marchand@redhat.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git