From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xie.rongqiang@zte.com.cn
Subject: [dpdk-test-report] |FAILURE| pw26047 [PATCH] app/testpmd:add bond type description
Date: 01 Jul 2017 00:25:01 -0700 [thread overview]
Message-ID: <e81775$12orv1e@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26047
_apply patch file failure_
Submitter: Xie RongQiang <xie.rongqiang@zte.com.cn>
Date: Fri, 30 Jun 2017 09:52:41 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
Repo:dpdk-next-crypto, Branch:master, CommitID:35b8eaf651395d4f869f50199594191970d8b7ca
Repo:dpdk-next-net, Branch:master, CommitID:143c03925695511f1bb692644982f643c0ede9bd
Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
Repo:dpdk, Branch:master, CommitID:46d1f3d1e73f7286e93cdf3c3e62ceefbdcf6cd3
Apply patch file failed:
Repo: dpdk
26047:
patching file app/test-pmd/cmdline.c
Hunk #1 FAILED at 4455.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-crypto
26047:
patching file app/test-pmd/cmdline.c
Hunk #1 FAILED at 4455.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-net
26047:
patching file app/test-pmd/cmdline.c
Hunk #1 FAILED at 4455.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-virtio
26047:
patching file app/test-pmd/cmdline.c
Hunk #1 FAILED at 4455.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-eventdev
26047:
patching file app/test-pmd/cmdline.c
Hunk #1 FAILED at 4455.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
DPDK STV team
reply other threads:[~2017-07-01 7:25 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='e81775$12orv1e@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xie.rongqiang@zte.com.cn \
/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).