From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(116515-116518) sid(24740) job(DTS_AUTO_1648) [V4, 4/4] test_plans/ice_iavf_fdir: add multicast new test case
Date: 20 Sep 2022 22:42:55 -0700 [thread overview]
Message-ID: <e2f6d4$ia6ajr@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/116518
Subject: [V4,4/4] test_plans/ice_iavf_fdir: add multicast new test case
_Testing issues_
Diff:
tests/TestSuite_ice_advanced_iavf_rss.py
test_plans/ice_advanced_iavf_rss_test_plan.rst
tests/TestSuite_ice_iavf_fdir.py
test_plans/ice_iavf_fdir_test_plan.rst
DPDK:
commit 1c9a7fba5c90e0422b517404499ed106f647bcff
Author: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Mon Jul 11 14:11:32 2022 +0200
Comment: net: accept unaligned data in checksum routines
DTS:
commit 1281a75942e15d3238e4215527dbe211b7d041e7
Author: hailinx xu <hailinx.xu@intel.com>
Date: Wed Sep 14 15:37:40 2022 +0800
Comment: tests/ice_advanced_rss: support ipv6 next protocol id
Test environment and result as below:
+-----------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+-----------------------+----------+--------------------------------+---------------------------------+
| ice_advanced_iavf_rss | CVL Only | not run | run |
+-----------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/5304b05a06e24d13940e86a9134488c9
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-09-21 5:43 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='e2f6d4$ia6ajr@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).