From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(82775) [8/8] examples/tep_termination: enhance getopt_long usage
Date: 29 Oct 2020 07:55:28 -0700 [thread overview]
Message-ID: <569c58$fvqmku@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/82775
_apply issues_
Submitter: Ibtisam Tariq <ibtisam.tariq@emumba.com>
Date: 2020-10-29 12:53:39
Reply_mail: 20201029125339.30916-8-ibtisam.tariq@emumba.com
DPDK git baseline:
Repo:dpdk-next-virtio, CommitID: 927ce56c9762a0fe1b18355eb94d0f77515529b2
Repo:dpdk, CommitID: f72299fd157deee129c5d8415f9a58b1af0bf84c
* Repo: dpdk-next-virtio
Falling back to patching base and 3-way merge...
Auto-merging examples/vhost/main.c
CONFLICT (content): Merge conflict in examples/vhost/main.c
error: Failed to merge in the changes.
Patch failed at 0006 examples/vhost: enhance getopt_long usage
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".
* Repo: dpdk
A examples/tep_termination/main.c
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): examples/tep_termination/main.c deleted in HEAD and modified in examples/tep_termination: enhance getopt_long usage. Version examples/tep_termination: enhance getopt_long usage of examples/tep_termination/main.c left in tree.
error: Failed to merge in the changes.
Patch failed at 0008 examples/tep_termination: enhance getopt_long usage
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:[~2020-10-29 14:55 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='569c58$fvqmku@orsmga005-auth.jf.intel.com' \
--to=sys_stv@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).