From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, ke1.xu@intel.com
Subject: [dts-test-report] |FAILURE| pw(121154-121156) sid(26207) job(DTS_AUTO_2133) [V1, 3/3] tests/vf_offload: implement packets count, super-long packet and random payload.
Date: 21 Dec 2022 01:15:01 -0800 [thread overview]
Message-ID: <1ac5b1$kac334@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/121156
Subject: [V1,3/3] tests/vf_offload: implement packets count, super-long packet and random payload.
_Apply issues_
Diff:
test_plans/vf_offload_test_plan.rst
tests/TestSuite_vf_offload.py
DPDK:
commit c581c49cd3fcaff596fbe566e270b442e6326c79
Author: Akhil Goyal <gakhil@marvell.com>
Date: Mon Dec 5 13:29:44 2022 +0530
Comment: maintainers: split baseband from crypto tree
DTS:
commit 275fc3485c4b172db8e7b96779850f187ba1bb6f
Author: Yogesh Jangra <yogesh.jangra@intel.com>
Date: Tue Nov 29 06:02:41 2022 +0000
Comment: tests/pipeline: added test case for validate instruction
DTS git baseline:
Repo:dts, CommitID: 275fc3485c4b172db8e7b96779850f187ba1bb6f
* Repo: dts
Falling back to patching base and 3-way merge...
Auto-merging test_plans/vf_offload_test_plan.rst
CONFLICT (content): Merge conflict in test_plans/vf_offload_test_plan.rst
error: Failed to merge in the changes.
Patch failed at 0001 test_plans/vf_offload: fix wrong example packets.
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-12-21 9:15 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='1ac5b1$kac334@orsmga008-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=ke1.xu@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).