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(114850-114851) sid(24278) job(DTS_AUTO_1443) [V1, 2/2] test_plans/kernelpf_iavf: remove duplicate case vf_tso
Date: 16 Aug 2022 06:19:57 -0700	[thread overview]
Message-ID: <e2f6d4$hvhsf2@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/114851
Subject: [V1,2/2] test_plans/kernelpf_iavf: remove duplicate case vf_tso

_Testing issues_

Diff:
	tests/TestSuite_kernelpf_iavf.py
	test_plans/kernelpf_iavf_test_plan.rst

DPDK:
	commit 72206323a5dd3182b13f61b25a64abdddfee595c
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Sat Jul 9 10:43:09 2022 +0200
	Comment: version: 22.11-rc0

DTS:
	commit 33659110602da75f0e4ee03e54a2a81e71f8ce75
	Author: Lingli Chen <linglix.chen@intel.com>
	Date:   Tue Jul 5 04:16:47 2022 -0400
	Comment: tests/distributor: modify script add novector path expect


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

Log path: /regression_dts/results/test/77bfa959fb9847f39953ce20d5967529

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.4 LTS
	Kernel: 5.11.0-37-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 VF
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 17/10/7/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 16/10/6/0/0
	
	Detail test results:
	+---------------------------------------+------------+---------------+
	| suit/case                             | with_patch | without_patch |
	+---------------------------------------+------------+---------------+
	| kernelpf_iavf/test_vf_port_start_stop | failed     | failed        |
	| kernelpf_iavf/test_vf_rss_hash_key    | failed     | failed        |
	| kernelpf_iavf/test_vf_tso             | n/a        | failed        |
	| kernelpf_iavf/test_vf_promisc_mode    | failed     | failed        |
	| kernelpf_iavf/test_vf_rss             | failed     | failed        |
	| kernelpf_iavf/test_vf_vlan_filter     | failed     | failed        |
	| kernelpf_iavf/test_vf_vlan_promisc    | failed     | failed        |
	| kernelpf_iavf/test_vf_broadcast       | passed     | passed        |
	| kernelpf_iavf/test_vf_multicast       | passed     | passed        |
	| kernelpf_iavf/test_vf_unicast         | passed     | passed        |
	| kernelpf_iavf/test_vf_mac_filter      | passed     | passed        |
	| kernelpf_iavf/test_vf_vlan_strip      | passed     | passed        |
	| kernelpf_iavf/test_vf_information     | passed     | passed        |
	| kernelpf_iavf/test_vf_basic_rxtx      | passed     | passed        |
	| kernelpf_iavf/test_vf_vlan_insertion  | passed     | passed        |
	| kernelpf_iavf/test_vf_rx_interrupt    | passed     | passed        |
	| kernelpf_iavf/test_vf_statistic_reset | passed     | passed        |
	+---------------------------------------+------------+---------------+

DPDK STV team

                 reply	other threads:[~2022-08-16 13:20 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='e2f6d4$hvhsf2@orsmga007-auth.jf.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).