From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(115759-115761) sid(24511) job(DTS_AUTO_1479) [V3, 3/3] tests/*:add 22.07 new feature, support in dcf mode
Date: 01 Sep 2022 19:11:17 -0700 [thread overview]
Message-ID: <b72376$gpkt05@orsmga003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/115761
Subject: [V3,3/3] tests/*:add 22.07 new feature, support in dcf mode
_Apply issues_
Diff:
framework/settings.py
framework/dts.py
test_plans/vf_vlan_test_plan.rst
test_plans/vf_smoke_test_plan.rst
test_plans/vf_rss_test_plan.rst
test_plans/vf_offload_test_plan.rst
test_plans/vf_macfilter_test_plan.rst
test_plans/kernelpf_iavf_test_plan.rst
tests/TestSuite_vf_vlan.py
tests/TestSuite_vf_smoke.py
tests/TestSuite_vf_rss.py
tests/TestSuite_vf_offload.py
tests/TestSuite_vf_macfilter.py
tests/TestSuite_kernelpf_iavf.py
DPDK:
commit 4aee6110bb10b0225fa9562f2e48af233a9058a1
Author: Huichao Cai <chcchc88@163.com>
Date: Mon Aug 8 09:48:12 2022 +0800
Comment: ip_frag: add IPv4 fragment copy
DTS:
commit 04a93b603b6102bad7608508ceae16f31ba59ad5
Author: Ke Xu <ke1.xu@intel.com>
Date: Tue Aug 23 05:59:39 2022 +0000
Comment: tests/tso: modify get_chksum_value_and_verify to improve the performance
DTS git baseline:
Repo:dts, CommitID: 04a93b603b6102bad7608508ceae16f31ba59ad5
* Repo: dts
Falling back to patching base and 3-way merge...
Auto-merging tests/TestSuite_vf_offload.py
CONFLICT (content): Merge conflict in tests/TestSuite_vf_offload.py
error: Failed to merge in the changes.
Patch failed at 0003 tests/*:add 22.07 new feature, support in dcf mode
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:[~2022-09-02 2:11 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='b72376$gpkt05@orsmga003-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).