From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(109734-109738) sid(22524) job(DTS_AUTO_757) [V1, 5/5] test_plans/index: add new testsuite
Date: 17 Apr 2022 23:10:54 -0700 [thread overview]
Message-ID: <28e406$fo8134@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2983 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/109738
Subject: [V1,5/5] test_plans/index: add new testsuite
_Testing issues_
Diff:
test_plans/loopback_virtio_user_server_mode_test_plan.rst
tests/TestSuite_loopback_virtio_user_server_mode.py
test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
tests/TestSuite_loopback_virtio_user_server_mode_cbdma.py
test_plans/index.rst
DPDK:
commit 76076342ec8ef108a155938d46a88bb493fae60e
Author: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Mon Apr 11 17:15:58 2022 +0200
Comment: eal: emit warning for unused trylock return value
DTS:
commit 24ae0a9a40dae26d27aa0ee79a75557135408add
Author: Yaqi Tang <yaqi.tang@intel.com>
Date: Wed Apr 6 22:23:11 2022 +0800
Comment: tests/cvl_iavf_fdir_pppol2tpoudp: modify test script for more fdir action
Test environment and result as below:
+----------------------------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+----------------------------------------+----------+---------------------------------+--------------------------------+
| loopback_virtio_user_server_mode_cbdma | Virtio | not run | run |
+----------------------------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/68e062b514ce478f9c4352d25157be53
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.3 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: Virtio
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 4/0/4/0/0
Detail test results:
+--------------------------------------------------------------------------------------------------------------------+------------+
| suit/case | with_patch |
+--------------------------------------------------------------------------------------------------------------------+------------+
| loopback_virtio_user_server_mode_cbdma/test_server_mode_split_ring_large_chain_packets_stress_test_with_cbdma | failed |
| loopback_virtio_user_server_mode_cbdma/test_server_mode_split_ring_all_path_multi_queues_payload_check_with_cbdma | failed |
| loopback_virtio_user_server_mode_cbdma/test_server_mode_packed_ring_large_chain_packets_stress_test_with_cbdma | failed |
| loopback_virtio_user_server_mode_cbdma/test_server_mode_packed_ring_all_path_multi_queues_payload_check_with_cbdma | failed |
+--------------------------------------------------------------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-04-18 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 6:10 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-18 6:19 sys_stv
2022-04-18 6:16 sys_stv
2022-04-18 4:17 sys_stv
2022-04-18 4:14 sys_stv
2022-04-17 3:34 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='28e406$fo8134@orsmga006-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).