From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weix.ling@intel.com
Subject: [dts-test-report] |FAILURE| pw(125348-125350) sid(27473) job(DTS_AUTO_2505) [V1, 3/3] tests/vswitch_sample_dsa: add new testsuite
Date: 20 Mar 2023 20:23:16 -0700 [thread overview]
Message-ID: <374626$jk3gb6@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4135 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/125350
Subject: [V1,3/3] tests/vswitch_sample_dsa: add new testsuite
_Testing issues_
Diff:
test_plans/index.rst
test_plans/vswitch_sample_dsa_test_plan.rst
tests/TestSuite_vswitch_sample_dsa.py
DPDK:
commit 33949800f1afcb7527b6e36c60c1548687ccb673
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Mon Mar 20 17:21:35 2023 +0100
Comment: version: 23.03-rc3
DTS:
commit 964b48e223f9f3d4f1fe60502f40be7f85a9f661
Author: Song Jiale <songx.jiale@intel.com>
Date: Mon Jan 16 15:00:02 2023 +0000
Comment: tests/shutdown_api: modify the command to adapt to the changes in ethtool
Test environment and result as below:
+--------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+--------------------+----------+--------------------------------+---------------------------------+
| vswitch_sample_dsa | CVL Only | not run | run |
+--------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/d5baf0e5ebfa44bca45f8ee3eb3aa666
#1: UB2004-64+216_columbiaville_25g
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: FAILURE
Catogory: CVL Only
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 0/0/0/0/0
with_patch Total/Pass/Fail/Blocked/NA: 12/0/12/0/0
Detail test results:
+-----------------------------------------------------------------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-----------------------------------------------------------------------------------------------------------------------+------------+---------------+
| vswitch_sample_dsa/test_vm2vm_virtio_user_forwarding_test_using_dsa_dpdk_driver | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_pmd_packed_ring_test_with_dsa_kernel_driver_register_and_unregister_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_split_ring_test_with_dsa_dpdk_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_user_forwarding_test_using_dsa_kernel_driver | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_split_ring_test_with_dsa_kernel_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_pmd_split_ring_test_with_dsa_kernle_driver_register_and_unregister_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_pmd_packed_ring_test_with_dsa_dpdk_driver_register_and_unregister_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_packed_ring_test_with_2_dsa_wq_with_dpdk_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_packed_ring_test_with_dsa_dpdk_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_packed_ring_test_with_dsa_kernel_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_net_packed_ring_test_with_2_dsa_wq_with_kernel_driver_and_iperf_stable_check | failed | n/a |
| vswitch_sample_dsa/test_vm2vm_virtio_pmd_split_ring_test_with_dsa_dpdk_driver_register_and_unregister_stable_check | failed | n/a |
+-----------------------------------------------------------------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2023-03-21 3:23 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='374626$jk3gb6@orsmga006-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=weix.ling@intel.com \
/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).