automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(107218-107219) sid(21587) job(DTS_AUTO_498) [V1, 2/2] tests/short_live: wait for interface up
Date: 10 Feb 2022 18:39:36 -0800	[thread overview]
Message-ID: <8ea9f5$k7sr5f@fmsmga001-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/107219
Subject: [V1,2/2] tests/short_live: wait for interface up

_Testing issues_

Diff:
	tests/TestSuite_kni.py
	tests/TestSuite_short_live.py

DPDK:
	commit 1d1126ad436e8c7c015fb3f67ad3af05c3b397d5
	Author: Bruce Richardson <bruce.richardson@intel.com>
	Date:   Thu Feb 10 15:42:38 2022 +0000
	Comment: vhost: fix C++ include

DTS:
	commit 49e00837278eacd61d6025594c720914c140bae2
	Author: Yaqi Tang <yaqi.tang@intel.com>
	Date:   Tue Feb 8 19:53:15 2022 +0000
	Comment: test_plans/cvl_switch_filter: add test plan for cvl switch filter support l4 mask


Test environment and result as below:
+------------+----------+---------------------------------+--------------------------------+
| suits      | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+------------+----------+---------------------------------+--------------------------------+
| kni        | NIC PF   | not run                         | run                            |
| short_live | NIC PF   | not run                         | run                            |
+------------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/73b0864cfb364eff8e5ee97e6fb97fd5

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.3 LTS
	Kernel: 5.8.0-51-generic
	CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
	GCC: gcc (GCC) 10.3.0
	Clang: 10.0.0-4ubuntu1


	Status: FAILURE
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 10/8/2/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 10/3/2/5/0
	
	Detail test results:
	+----------------------------------------------+------------+---------------+
	| suit/case                                    | with_patch | without_patch |
	+----------------------------------------------+------------+---------------+
	| short_live/test_clean_up_with_signal_l2fwd   | failed     | failed        |
	| short_live/test_clean_up_with_signal_l3fwd   | failed     | failed        |
	| short_live/test_start_up_time                | passed     | passed        |
	| short_live/test_clean_up_with_signal_testpmd | passed     | passed        |
	| kni/test_statistics                          | blocked    | passed        |
	| kni/test_stress                              | blocked    | passed        |
	| kni/test_ping                                | blocked    | passed        |
	| kni/test_tcpdump                             | blocked    | passed        |
	| kni/test_ifconfig                            | blocked    | passed        |
	| short_live/test_basic_forwarding             | passed     | passed        |
	+----------------------------------------------+------------+---------------+

DPDK STV team

                 reply	other threads:[~2022-02-11  2:39 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='8ea9f5$k7sr5f@fmsmga001-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=test-report@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).