From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(102731-102733) sid(19941) job(DTS_AUTO869) [V1, 3/3] tests/generic_flow_api: add case:test_fdir_for_match_report
Date: 27 Oct 2021 21:12:34 -0700 [thread overview]
Message-ID: <311d4e$iuh0k2@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/102733
Subject: [V1,3/3] tests/generic_flow_api: add case:test_fdir_for_match_report
_Apply issues_
Diff:
test_plans/fdir_test_plan.rst
test_plans/generic_flow_api_test_plan.rst
tests/TestSuite_generic_flow_api.py
conf/test_case_supportlist.json
DPDK:
commit 452c1916b0dbb414a28dff89c995253da1c23c0b
Author: Kevin Laatz <kevin.laatz@intel.com>
Date: Tue Oct 26 14:20:45 2021 +0000
Comment: dma/idxd: fix truncated error code in status check
DTS:
commit bf4f2a0643bceea4442ca552456265f661e58968
Author: Zou Ping <pingx.zou@intel.com>
Date: Wed Oct 27 19:58:14 2021 +0800
Comment: test_plans/cvl_switch_filter_pppoe: change ppp port to bytes type
DTS git baseline:
Repo:dts, CommitID: bf4f2a0643bceea4442ca552456265f661e58968
* Repo: dts
Falling back to patching base and 3-way merge...
Auto-merging tests/TestSuite_generic_flow_api.py
CONFLICT (content): Merge conflict in tests/TestSuite_generic_flow_api.py
error: Failed to merge in the changes.
Patch failed at 0003 tests/generic_flow_api: add case:test_fdir_for_match_report
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-10-28 4:12 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='311d4e$iuh0k2@fmsmga001-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).