From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(110124-110126) sid(22625) job(DTS_AUTO_800) [V1, 3/3] tests/vm2vm_virtio_user_cbdma: add vm2vm_virtio_user_cbdma testsuite
Date: 24 Apr 2022 08:03:26 -0700 [thread overview]
Message-ID: <8ea9f5$kvjbb3@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4475 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/110126
Subject: [V1,3/3] tests/vm2vm_virtio_user_cbdma: add vm2vm_virtio_user_cbdma testsuite
_Testing issues_
Diff:
test_plans/index.rst
test_plans/vm2vm_virtio_user_cbdma_test_plan.rst
tests/TestSuite_vm2vm_virtio_user_cbdma.py
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 8beb7c0f74d0d45bb55fe2a6010a38c2089c6340
Author: Jun Dong <junx.dong@intel.com>
Date: Wed Apr 20 15:04:20 2022 +0800
Comment: framework/logger: fix bug of generate the log output path
Test environment and result as below:
+-------------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-------------------------+----------+---------------------------------+--------------------------------+
| vm2vm_virtio_user_cbdma | Virtio | not run | run |
+-------------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/daed548340df4b9fa62110e2c78b57e5
#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: 14/0/14/0/0
Detail test results:
+----------------------------------------------------------------------------------------------------------------------------------------+------------+
| suit/case | with_patch |
+----------------------------------------------------------------------------------------------------------------------------------------+------------+
| vm2vm_virtio_user_cbdma/test_split_ring_vectorized_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_split_ring_non_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_split_ring_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_split_ring_inorder_non_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_split_ring_inorder_mergeable_path_multi_queues_test_non_indirect_descriptor_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_split_ring_inorder_mergeable_path_multi_queues_test_indirect_descriptor_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_vectorized_tx_path_test_batch_processing_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_vectorized_tx_path_multi_queues_test_indirect_descriptor_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_non_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_inorder_vectorized_rx_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_inorder_vectorized_path_multi_queues_check_with_ring_size_is_not_power_of_2_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_inorder_non_mergeable_path_multi_queues_with_cbdma | failed |
| vm2vm_virtio_user_cbdma/test_packed_ring_inorder_mergeable_path_multi_queues_with_cbdma | failed |
+----------------------------------------------------------------------------------------------------------------------------------------+------------+
DPDK STV team
reply other threads:[~2022-04-24 15:03 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='8ea9f5$kvjbb3@fmsmga001-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).