From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, songx.jiale@intel.com
Subject: [dts-test-report] |FAILURE| pw(119245) sid(25464) job(DTS_AUTO_1783) [v1] tests/rte_flow_common: optimize scripts
Date: 27 Oct 2022 23:13:02 -0700 [thread overview]
Message-ID: <b63a69$i6b5f0@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/119245
Subject: [v1] tests/rte_flow_common: optimize scripts
_Testing issues_
Diff:
tests/rte_flow_common.py
DPDK:
commit 9082336048e8c5779c1b4f8930041a42e9197348
Author: Chaoyong He <chaoyong.he@corigine.com>
Date: Tue Oct 25 15:59:18 2022 +0800
Comment: net/nfp: support new solution for tunnel decap action
DTS:
commit 878a9c7ea3b073956c4efc8cf21ac43454b1b336
Author: Zhimin Huang <zhiminx.huang@intel.com>
Date: Mon Oct 10 07:42:43 2022 +0800
Comment: tests/ice_dcf_qos:modify the command according to the dpdk changed
Test environment and result as below:
+-----------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-----------------------+----------+---------------------------------+--------------------------------+
| ice_advanced_iavf_rss | CVL Only | run | not run |
| l2tp_esp_coverage | CVL Only | run | not run |
+-----------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/744ac7468d7d4d97939fd32dfed401f4
Detail execution results:
There were no deltas reported. There may have been an issue with the test harness.
DPDK STV team
reply other threads:[~2022-10-28 6:13 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='b63a69$i6b5f0@orsmga006-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=songx.jiale@intel.com \
--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).