* [dpdk-dev] Recent failure in autotest
@ 2020-09-22 23:11 Stephen Hemminger
2020-09-23 7:45 ` David Marchand
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Hemminger @ 2020-09-22 23:11 UTC (permalink / raw)
To: dev
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] Recent failure in autotest
2020-09-22 23:11 [dpdk-dev] Recent failure in autotest Stephen Hemminger
@ 2020-09-23 7:45 ` David Marchand
0 siblings, 0 replies; 2+ messages in thread
From: David Marchand @ 2020-09-23 7:45 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: dev
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-09-23 7:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-22 23:11 [dpdk-dev] Recent failure in autotest Stephen Hemminger
2020-09-23 7:45 ` David Marchand
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).