From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(116864) sid(24826) job(DTS_AUTO_1711) [V1] tests/virtio_user_as_exceptional_path: modify testsuite syncwith testplan
Date: 29 Sep 2022 02:31:48 -0700 [thread overview]
Message-ID: <d1365c$l6bjfg@fmsmga003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/116864
Subject: [V1] tests/virtio_user_as_exceptional_path: modify testsuite syncwith testplan
_Testing issues_
Diff:
tests/TestSuite_virtio_user_as_exceptional_path.py
DPDK:
commit bbbe6c596b284909e4112ac9573b16da2137ffab
Author: Akhil Goyal <gakhil@marvell.com>
Date: Wed Sep 28 17:52:53 2022 +0530
Comment: security: support MACsec
DTS:
commit 8071f2b95380dc052114974dce8bddb8fa1edc04
Author: Song Jiale <songx.jiale@intel.com>
Date: Fri Sep 23 14:04:00 2022 +0000
Comment: tests/iavf_fdir_protocol_agnostic_flow: add test case for ice protocol agnostic flow offloading
Test environment and result as below:
+---------------------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------------------------------+----------+--------------------------------+---------------------------------+
| virtio_user_as_exceptional_path | Virtio | run | not run |
+---------------------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/e014ef8e9af9483cb0a4a4c123049a93
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.4 LTS
Kernel: 5.11.0-37-generic
CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: 10.0.0-4ubuntu1
Status: FAILURE
Catogory: Virtio
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 2/0/2/0/0
with_patch Total/Pass/Fail/Blocked/NA: 1/0/1/0/0
Detail test results:
+----------------------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+----------------------------------------------------------------------------+------------+---------------+
| virtio_user_as_exceptional_path/test_vhost_exception_path_NIC_original | n/a | failed |
| virtio_user_as_exceptional_path/test_vhost_exception_path_TAP_original | n/a | failed |
| virtio_user_as_exceptional_path/test_vhost_exception_path_with_virtio_user | failed | n/a |
+----------------------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2022-09-29 9:32 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='d1365c$l6bjfg@fmsmga003-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).