From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(112742-112743) sid(23525) job(DTS_AUTO_1210) [V1, 2/2] tests/l3fwdacl: merge l3fwd-acl with l3fwd and fix to support different force-max-simd-bitwidth
Date: 14 Jun 2022 22:48:41 -0700 [thread overview]
Message-ID: <f10ab6$hhk4ra@fmsmga007-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/112743
Subject: [V1,2/2] tests/l3fwdacl: merge l3fwd-acl with l3fwd and fix to support different force-max-simd-bitwidth
_Testing OK_
Diff:
test_plans/l3fwdacl_test_plan.rst
tests/TestSuite_l3fwdacl.py
conf/app_name.cfg
DPDK:
commit 1ab4156e7d57858fca1db448ac7a0792e1d527b6
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Wed Jun 8 21:43:41 2022 +0200
Comment: version: 22.07-rc1
DTS:
commit 57cad1a6020b798bda6e5247023a044746dd9dff
Author: Jiale Song <songx.jiale@intel.com>
Date: Wed May 25 19:19:34 2022 +0800
Comment: tests/vf_rss: remove ip fragment packets
Test environment and result as below:
+----------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+----------+----------+---------------------------------+--------------------------------+
| l3fwdacl | NIC PF | not run | run |
+----------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/e9c4bed7b3dd4156ba7d98794afeda5d
#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: SUCCESS
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 5/5/0/0/0
Detail test results:
+------------------------------------+------------+
| suit/case | with_patch |
+------------------------------------+------------+
| l3fwdacl/test_l3fwdacl_acl_rule | passed |
| l3fwdacl/test_l3fwdacl_exact_route | passed |
| l3fwdacl/test_l3fwdacl_invalid | passed |
| l3fwdacl/test_l3fwdacl_lpm_route | passed |
| l3fwdacl/test_l3fwdacl_scalar | passed |
+------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-06-15 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 5:48 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-15 5:41 sys_stv
2022-06-15 5:39 sys_stv
2022-06-15 5:38 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='f10ab6$hhk4ra@fmsmga007-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).