From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |WARNING| pw(95233) sid(17604) [V2, 1/5] examples/pipeline: improve table update CLI commands
Date: 22 Jul 2021 03:35:28 -0700 [thread overview]
Message-ID: <f5489b$dhkbcf@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/95233
_apply issues_
Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: 2021-07-02 22:39:49
Reply_mail: 20210702223949.65944-1-cristian.dumitrescu@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: d3c521265eddf9fe604167e1b902909cb65f426b
* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: examples/pipeline/cli.c:1038
error: examples/pipeline/cli.c: patch does not apply
error: patch failed: examples/pipeline/examples/vxlan.cli:22
error: examples/pipeline/examples/vxlan.cli: patch does not apply
error: patch failed: examples/pipeline/examples/vxlan_pcap.cli:17
error: examples/pipeline/examples/vxlan_pcap.cli: patch does not apply
Applying: examples/pipeline: improve table update CLI commands
Patch failed at 0001 examples/pipeline: improve table update CLI commands
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
next reply other threads:[~2021-07-22 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 10:35 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-22 7:37 sys_stv
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='f5489b$dhkbcf@orsmga007-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).