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(108561-108562) sid(22039) job(DTS_AUTO_628) [V2, 2/2] test_plan/vf_daemon: sync add step dpdk pf set mtu.
Date: 07 Mar 2022 18:19:40 -0800	[thread overview]
Message-ID: <8ea9f5$kfspq4@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/108562
Subject: [V2,2/2] test_plan/vf_daemon: sync add step dpdk pf set mtu.

_Testing issues_

Diff:
	tests/TestSuite_vf_daemon.py
	test_plans/vf_daemon_test_plan.rst

DPDK:
	commit 6eccb0c9eea51089ce14bff92697245eb342963b
	Author: Haiyue Wang <haiyue.wang@intel.com>
	Date:   Mon Mar 7 18:25:56 2022 +0800
	Comment: graph: remove useless duplicate name check

DTS:
	commit fb043ef7231bcd8910fa55b072e2900d5cf2b5b5
	Author: Weiyuan Li <weiyuanx.li@intel.com>
	Date:   Fri Feb 11 14:26:10 2022 +0800
	Comment: test_plans/userspace_ethtool:remove duplicate vlan test case.


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

Log path: /regression_dts/results/test/541bfa114a27413d8bf966896d7cf149

#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 VF
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 14/0/12/0/2
	with_patch Total/Pass/Fail/Blocked/NA: 14/0/12/0/2
	
	Detail test results:
	+------------------------------------+------------+---------------+
	| suit/case                          | with_patch | without_patch |
	+------------------------------------+------------+---------------+
	| vf_daemon/test_vlan_strip          | failed     | failed        |
	| vf_daemon/test_vlan_tag            | failed     | failed        |
	| vf_daemon/test_broadcast_mode      | failed     | failed        |
	| vf_daemon/test_stats_show_clear    | failed     | failed        |
	| vf_daemon/test_promisc_mode        | failed     | failed        |
	| vf_daemon/test_vlan_filter         | failed     | failed        |
	| vf_daemon/test_vlan_insert         | failed     | failed        |
	| vf_daemon/test_vf_mac_set          | failed     | failed        |
	| vf_daemon/test_multicast_mode      | failed     | failed        |
	| vf_daemon/test_tx_loopback         | failed     | failed        |
	| vf_daemon/test_vlan_antispoof      | failed     | failed        |
	| vf_daemon/test_vf_mtu              | failed     | failed        |
	| vf_daemon/test_ixgbe_vf_jumboframe | n/a        | n/a           |
	| vf_daemon/test_all_queues_drop     | n/a        | n/a           |
	+------------------------------------+------------+---------------+

DPDK STV team

                 reply	other threads:[~2022-03-08  2:19 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$kfspq4@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).