From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(121604-121605) sid(26393) job(DTS_AUTO_2289) [V1, 2/2] tests/vf_pf_reset: add new cases according to testplan
Date: 04 Jan 2023 23:20:35 -0800 [thread overview]
Message-ID: <d60617$jaojb1@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2628 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/121605
Subject: [V1,2/2] tests/vf_pf_reset: add new cases according to testplan
_Testing OK_
Diff:
test_plans/vf_pf_reset_test_plan.rst
tests/TestSuite_vf_pf_reset.py
DPDK:
commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 13 16:07:10 2022 +0100
Comment: ci: drop Travis configuration
DTS:
commit f036e7097fe1079c36d566ebef57c2328f5eb865
Author: Song Jiale <songx.jiale@intel.com>
Date: Wed Jan 4 11:29:43 2023 +0000
Comment: test_plans/multiprocess: optimize the testplan format
Test environment and result as below:
+-------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-------------+----------+---------------------------------+--------------------------------+
| vf_pf_reset | NIC VF | not run | run |
+-------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/3e74dc067aba4021bc239d057e24ea08
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.5 LTS
Kernel: 5.4.0-135-generic
CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: NA
Status: SUCCESS
Catogory: NIC VF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 11/11/0/0/0
Detail test results:
+-----------------------------------------------------+------------+
| suit/case | with_patch |
+-----------------------------------------------------+------------+
| vf_pf_reset/test_2vfs_passed_through_to_2VM | passed |
| vf_pf_reset/test_create_1vf_on_each_pf | passed |
| vf_pf_reset/test_create_2vfs_on_1pf | passed |
| vf_pf_reset/test_create_2vfs_on_1pf_separately_pmd | passed |
| vf_pf_reset/test_mac_address_restore | passed |
| vf_pf_reset/test_pf_reset_trigger_vf_reset | passed |
| vf_pf_reset/test_vfs_passed_through_to_1VM | passed |
| vf_pf_reset/test_vlan_rx_restore_create_vf_each_pf | passed |
| vf_pf_reset/test_vlan_rx_restore_vf_reset_1port | passed |
| vf_pf_reset/test_vlan_rx_restore_vf_reset_all_ports | passed |
| vf_pf_reset/test_vlan_tx_restore | passed |
+-----------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-01-05 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 7:20 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 6:35 sys_stv
2023-01-05 6:33 sys_stv
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='d60617$jaojb1@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).