From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(101549) sid(19629) job(DTS_AUTO763) [V1] tests/rteflow_priority: add mark to fdir rule
Date: 13 Oct 2021 22:59:32 -0700 [thread overview]
Message-ID: <722c05$eaq83u@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/101549
Subject: [V1] tests/rteflow_priority: add mark to fdir rule
_Testing issues_
Diff:
tests/TestSuite_rteflow_priority.py
test_plans/rteflow_priority_test_plan.rst
DPDK:
commit d75eed0fbe4b942bc6df2e2908a8b5c2c30c99aa
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed Sep 1 16:49:44 2021 -0700
Comment: mbuf: fix typo in comment
DTS:
commit b082e251348d7c20e09243a742136e6d93626fab
Author: Thinh Tran <thinhtr@linux.vnet.ibm.com>
Date: Thu Sep 30 17:20:51 2021 +0000
Comment: Framework:fix the first numa node may not be '0'
Test environment and result as below:
+------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+------------------+----------+--------------------------------+---------------------------------+
| rteflow_priority | CVL Only | not run | run |
+------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/753f5aa4827e4a4ca6e6a3d726326d9c
#1: 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: FAILURE
Catogory: CVL Only
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 6/5/1/0/0
with_patch Total/Pass/Fail/Blocked/NA: 6/5/1/0/0
Detail test results:
+-------------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-------------------------------------------------------------------+------------+---------------+
| rteflow_priority/test_priority_in_nonpipeline_mode | failed | failed |
| rteflow_priority/test_create_fdir_rule_with_priority_0 | passed | passed |
| rteflow_priority/test_priority_in_pipeline_mode | passed | passed |
| rteflow_priority/test_no_destination_high_prority | passed | passed |
| rteflow_priority/test_create_switch_rule_with_priority_1 | passed | passed |
| rteflow_priority/test_rules_with_same_parameters_different_action | passed | passed |
+-------------------------------------------------------------------+------------+---------------+
DPDK STV team
next reply other threads:[~2021-10-14 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 5:59 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-14 5: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='722c05$eaq83u@orsmga007-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).