From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(111055-111056) sid(22911) job(DTS_AUTO_1024) [V3, 2/2] tests/multiprocess: add pf multiprocess test case
Date: 12 May 2022 04:20:02 -0700 [thread overview]
Message-ID: <003cea$hn2csq@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3284 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/111056
Subject: [V3,2/2] tests/multiprocess: add pf multiprocess test case
_Testing issues_
Diff:
test_plans/multiprocess_test_plan.rst
tests/TestSuite_multiprocess.py
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_columbiaville_25g | UB2004-64+216_fortville_spirit |
+--------------+----------+---------------------------------+--------------------------------+
| multiprocess | NIC PF | not run | run |
+--------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/2a31707aa6f24908929f467f498dde00
#1: UB2004-64+216_fortville_spirit
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: FAILURE
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 4/4/0/0/0
with_patch Total/Pass/Fail/Blocked/NA: 14/10/4/0/0
Detail test results:
+------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+------------------------------------------------------------+------------+---------------+
| multiprocess/test_multiprocess_proc_type_random_packet | failed | n/a |
| multiprocess/test_multiprocess_with_rss_symmetric | failed | n/a |
| multiprocess/test_multiprocess_with_fdir_rule | failed | n/a |
| multiprocess/test_multiprocess_symmetric_mp_packet | failed | n/a |
| multiprocess/test_multiprocess_proc_type_specify_packet | passed | n/a |
| multiprocess/test_multiprocess_with_rss_toeplitz | passed | n/a |
| multiprocess/test_multiprocess_simple_mpapplicationstartup | passed | passed |
| multiprocess/test_multiprocess_simple_mpnoflag | passed | passed |
| multiprocess/test_multiprocess_simple_mploadtest | passed | passed |
| multiprocess/test_multiprocess_auto_process_type_detected | passed | n/a |
| multiprocess/test_multiprocess_simple_mpbasicoperation | passed | passed |
| multiprocess/test_multiprocess_negative_2_primary_process | passed | n/a |
| multiprocess/test_multiprocess_negative_exceed_process_num | passed | n/a |
| multiprocess/test_multiprocess_server_client_mp_packet | passed | n/a |
+------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2022-05-12 11:20 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='003cea$hn2csq@orsmga008-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).