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(112031) sid(23233) job(DTS_AUTO_1160) [V1] tests/vf_pf_reset: add vf_pf_reset testsuite
Date: 30 May 2022 22:38:27 -0700	[thread overview]
Message-ID: <87f1b2$h5h59h@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/112031
Subject: [V1] tests/vf_pf_reset: add vf_pf_reset testsuite

_Testing issues_

Diff:
	tests/TestSuite_vf_pf_reset.py
	conf/vf_pf_reset.cfg

DPDK:
	commit 64fcadeac0f70c8c9c215196a3d580b4ad37dcdc
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Tue May 3 14:03:21 2022 +0200
	Comment: avoid AltiVec keyword vector

DTS:
	commit 57cad1a6020b798bda6e5247023a044746dd9dff
	Author: Jiale Song <songx.jiale@intel.com>
	Date:   Wed May 25 19:19:34 2022 +0800
	Comment: tests/vf_rss: remove ip fragment packets


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

Log path: /regression_dts/results/test/adbe55e334f14217893ded405344c9a9

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.4 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
	with_patch Total/Pass/Fail/Blocked/NA: 10/0/10/0/0
	
	Detail test results:
	+-----------------------------------------------------+------------+
	| suit/case                                           | with_patch |
	+-----------------------------------------------------+------------+
	| vf_pf_reset/test_vlan_tx_restore                    | failed     |
	| vf_pf_reset/test_vlan_rx_restore_vf_reset_all_ports | failed     |
	| vf_pf_reset/test_vlan_rx_restore_vf_reset_1port     | failed     |
	| vf_pf_reset/test_vlan_rx_restore_create_vf_each_pf  | failed     |
	| vf_pf_reset/test_vfs_passed_through_to_1VM          | failed     |
	| vf_pf_reset/test_mac_address_restore                | failed     |
	| vf_pf_reset/test_create_2vfs_on_1pf_separately_pmd  | failed     |
	| vf_pf_reset/test_create_2vfs_on_1pf                 | failed     |
	| vf_pf_reset/test_create_1vf_on_each_pf              | failed     |
	| vf_pf_reset/test_2vfs_passed_through_to_2VM         | failed     |
	+-----------------------------------------------------+------------+

DPDK STV team

                 reply	other threads:[~2022-05-31  5: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='87f1b2$h5h59h@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).