From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(102498) sid(19855) job(DTS_AUTO840) [V2] smoke test support config different queues
Date: 22 Oct 2021 12:15:23 -0700 [thread overview]
Message-ID: <311d4e$is3o48@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3053 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/102498
Subject: [V2] smoke test support config different queues
_Testing issues_
Diff:
tests/smoke_base.py
tests/TestSuite_vf_smoke.py
tests/TestSuite_pf_smoke.py
test_plans/vf_smoke_test_plan.rst
test_plans/pf_smoke_test_plan.rst
DPDK:
commit a188277d5357dd3c7957070650aaac0027bf69dd
Author: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu Oct 21 20:59:38 2021 +0800
Comment: dmadev: fix debug build
DTS:
commit d92d61bbfa39ed03e06311566be1dffd4df3a872
Author: Yan Xia <yanx.xia@intel.com>
Date: Wed Sep 29 18:28:32 2021 +0000
Comment: tests/generic_flow_api: move case from generic_filter to generic_flow_api
Test environment and result as below:
+----------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+----------+----------+---------------------------------+--------------------------------+
| pf_smoke | CVL Only | run | not run |
| vf_smoke | NIC VF | not run | run |
+----------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/6be7c8a8cc89452198e32f54e5a88b7d
#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: NIC VF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 3/3/0/0/0
with_patch Total/Pass/Fail/Blocked/NA: 3/2/1/0/0
Detail test results:
+-------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-------------------------------+------------+---------------+
| vf_smoke/test_vf_tx_rx_queue | failed | passed |
| vf_smoke/test_vf_rss | passed | passed |
| vf_smoke/test_vf_jumbo_frames | passed | passed |
+-------------------------------+------------+---------------+
#2: UB2004-64+216_columbiaville_25g
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: SUCCESS
Catogory: CVL Only
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 3/3/0/0/0
with_patch Total/Pass/Fail/Blocked/NA: 3/3/0/0/0
Detail test results:
+-------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-------------------------------+------------+---------------+
| pf_smoke/test_pf_jumbo_frames | passed | passed |
| pf_smoke/test_pf_tx_rx_queue | passed | passed |
| pf_smoke/test_pf_rss | passed | passed |
+-------------------------------+------------+---------------+
DPDK STV team
next reply other threads:[~2021-10-22 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 19:15 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-22 18:54 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='311d4e$is3o48@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).