From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(112208-112209) sid(23286) job(DTS_AUTO_1170) [V1, 2/2] tests/vf_vlan: modify script VLAN filter enable requires a port VLAN is assigned
Date: 01 Jun 2022 06:24:26 -0700 [thread overview]
Message-ID: <003cea$i25kkj@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4168 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/112209
Subject: [V1,2/2] tests/vf_vlan: modify script VLAN filter enable requires a port VLAN is assigned
_Testing issues_
Diff:
tests/TestSuite_kernelpf_iavf.py
tests/TestSuite_vf_vlan.py
DPDK:
commit 531c98fd751ccf868fde65c69a59a8380931a981
Author: Chaoyong He <chaoyong.he@corigine.com>
Date: Tue May 17 11:02:22 2022 +0800
Comment: maintainers: update for nfp
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 |
+---------------+----------+--------------------------------+---------------------------------+
| kernelpf_iavf | NIC VF | run | not run |
| vf_vlan | NIC VF | run | not run |
+---------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/d00b48fc96b14defb636b1f0b933a654
#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
without_patch Total/Pass/Fail/Blocked/NA: 28/13/15/0/0
with_patch Total/Pass/Fail/Blocked/NA: 28/13/15/0/0
Detail test results:
+-------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-------------------------------------------+------------+---------------+
| kernelpf_iavf/test_vf_port_start_stop | failed | failed |
| kernelpf_iavf/test_vf_basic_rxtx | passed | failed |
| kernelpf_iavf/test_vf_promisc_mode | failed | failed |
| kernelpf_iavf/test_vf_add_pvid | failed | failed |
| kernelpf_iavf/test_vf_tso | failed | failed |
| kernelpf_iavf/test_vf_vlan_promisc | failed | passed |
| kernelpf_iavf/test_vf_rss_hash_key | failed | failed |
| kernelpf_iavf/test_vf_sw_checksum_offload | failed | failed |
| kernelpf_iavf/test_vf_vlan_filter | failed | failed |
| kernelpf_iavf/test_vf_rss | failed | failed |
| vf_vlan/test_add_pvid_vf | failed | failed |
| kernelpf_iavf/test_vf_with_jumboframe | failed | failed |
| kernelpf_iavf/test_vf_vlan_insertion | failed | failed |
| kernelpf_iavf/test_vf_hw_checksum_offload | failed | failed |
| kernelpf_iavf/test_vf_vlan_rx | failed | failed |
| kernelpf_iavf/test_vf_vlan_strip | failed | failed |
| vf_vlan/test_vf_vlan_tx | passed | passed |
| vf_vlan/test_vf_vlan_strip | passed | passed |
| kernelpf_iavf/test_vf_broadcast | passed | passed |
| kernelpf_iavf/test_vf_statistic_reset | passed | passed |
| kernelpf_iavf/test_vf_multicast | passed | passed |
| kernelpf_iavf/test_vf_mac_filter | passed | passed |
| kernelpf_iavf/test_vf_rx_interrupt | passed | passed |
| vf_vlan/test_pvid_vf_tx | passed | passed |
| kernelpf_iavf/test_vf_without_jumboframe | passed | passed |
| kernelpf_iavf/test_vf_information | passed | passed |
| kernelpf_iavf/test_vf_unicast | passed | passed |
| vf_vlan/test_vf_vlan_rx | passed | passed |
+-------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2022-06-01 13:24 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='003cea$i25kkj@orsmga008-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).