From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(111057-111058) sid(22912) job(DTS_AUTO_1028) [V3, 1/2] test_plans/multiprocess: add vf multiprocess test case
Date: 15 May 2022 23:19:34 -0700 [thread overview]
Message-ID: <7758ae$m2oa8i@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3094 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/111058
Subject: [V3,1/2] test_plans/multiprocess: add vf multiprocess test case
_Testing OK_
Diff:
tests/TestSuite_multiprocess_iavf.py
test_plans/multiprocess_iavf_test_plan.rst
test_plans/index.rst
DPDK:
commit c0c305ee9e0e7c9feca6412266a778f330d20c19
Author: David Marchand <david.marchand@redhat.com>
Date: Thu May 5 11:29:52 2022 +0200
Comment: ci: build some job with ASan
DTS:
commit e82d3bc030d87966a093852b326f6d675d65cb03
Author: Jun Dong <junx.dong@intel.com>
Date: Tue May 10 17:54:31 2022 +0800
Comment: tests/*: replace codename in test suites
Test environment and result as below:
+-------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+-------------------+----------+--------------------------------+---------------------------------+
| multiprocess_iavf | CVL Only | not run | run |
+-------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/e609f7bdc0ee40828178dda1d57c1f66
#1: UB2004-64+216_columbiaville_25g
OS: Ubuntu 20.04.4 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
with_patch Total/Pass/Fail/Blocked/NA: 14/14/0/0/0
Detail test results:
+-----------------------------------------------------------------+------------+
| suit/case | with_patch |
+-----------------------------------------------------------------+------------+
| multiprocess_iavf/test_multiprocess_auto_process_type_detected | passed |
| multiprocess_iavf/test_multiprocess_negative_2_primary_process | passed |
| multiprocess_iavf/test_multiprocess_negative_exceed_process_num | passed |
| multiprocess_iavf/test_multiprocess_proc_type_random_packet | passed |
| multiprocess_iavf/test_multiprocess_proc_type_specify_packet | passed |
| multiprocess_iavf/test_multiprocess_server_client_mp_packet | passed |
| multiprocess_iavf/test_multiprocess_simple_mpapplicationstartup | passed |
| multiprocess_iavf/test_multiprocess_simple_mpbasicoperation | passed |
| multiprocess_iavf/test_multiprocess_simple_mploadtest | passed |
| multiprocess_iavf/test_multiprocess_simple_mpnoflag | passed |
| multiprocess_iavf/test_multiprocess_symmetric_mp_packet | passed |
| multiprocess_iavf/test_multiprocess_with_fdir_rule | passed |
| multiprocess_iavf/test_multiprocess_with_rss_symmetric | passed |
| multiprocess_iavf/test_multiprocess_with_rss_toeplitz | passed |
+-----------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-05-16 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 6:19 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 6:00 sys_stv
2022-05-16 5:58 sys_stv
2022-05-16 5:57 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='7758ae$m2oa8i@orsmga005-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).