From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: qi.z.zhang@intel.com
Subject: [dpdk-test-report] |FAILURE| pw18023 [PATCH v3 18/29] app/testpmd: use VFD APIs on i40e
Date: 15 Dec 2016 22:13:57 -0800 [thread overview]
Message-ID: <9ddf0d$10otrmt@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3776 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/18023
_apply patch file failure_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Thu, 15 Dec 2016 16:04:52 -0500
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:d753dc372ec556c1c4e2ff4966a10c7441df7ea6
Repo:dpdk-next-net, Branch:master, CommitID:537fb4de02b90637320427f36e447f6243c01867
Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
Repo:dpdk, Branch:master, CommitID:c431384c8fbf8503693bcae1bdcd58d6fa459b8a
Apply patch file failed:
Repo: dpdk-next-crypto
18023:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline.c
Hunk #6 FAILED at 6611.
Hunk #7 FAILED at 6672.
Hunk #8 succeeded at 4124 with fuzz 2 (offset -2632 lines).
Hunk #9 FAILED at 6822.
Hunk #10 succeeded at 11453 with fuzz 2 (offset 4568 lines).
Hunk #11 FAILED at 6953.
Hunk #12 FAILED at 7032.
Hunk #13 FAILED at 10803.
Hunk #14 FAILED at 10857.
Hunk #15 FAILED at 10872.
Hunk #16 FAILED at 10945.
Hunk #17 FAILED at 10960.
Hunk #18 FAILED at 11033.
Hunk #19 FAILED at 11047.
Hunk #20 FAILED at 11119.
Hunk #21 FAILED at 11133.
Hunk #22 FAILED at 11196.
Hunk #23 FAILED at 11210.
Hunk #24 FAILED at 11495.
Hunk #25 succeeded at 11610 (offset -39 lines).
Hunk #26 FAILED at 11661.
18 out of 26 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-net
18023:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline.c
Hunk #14 FAILED at 10850.
Hunk #15 succeeded at 10862 (offset -3 lines).
Hunk #16 FAILED at 10941.
Hunk #17 succeeded at 10950 (offset -6 lines).
Hunk #18 FAILED at 11032.
Hunk #19 succeeded at 11037 (offset -9 lines).
Hunk #20 FAILED at 11121.
Hunk #21 succeeded at 11123 (offset -12 lines).
Hunk #22 FAILED at 11201.
Hunk #23 succeeded at 11200 (offset -15 lines).
Hunk #24 succeeded at 11468 (offset -35 lines).
Hunk #25 succeeded at 11621 (offset -35 lines).
Hunk #26 succeeded at 11633 (offset -35 lines).
5 out of 26 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk-next-virtio
18023:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline.c
Hunk #6 FAILED at 6611.
Hunk #7 FAILED at 6672.
Hunk #8 succeeded at 4117 with fuzz 2 (offset -2639 lines).
Hunk #9 FAILED at 6822.
Hunk #10 succeeded at 11405 with fuzz 2 (offset 4520 lines).
Hunk #11 FAILED at 6953.
Hunk #12 FAILED at 7032.
Hunk #13 FAILED at 10803.
Hunk #14 FAILED at 10857.
Hunk #15 FAILED at 10872.
Hunk #16 FAILED at 10945.
Hunk #17 FAILED at 10960.
Hunk #18 FAILED at 11033.
Hunk #19 FAILED at 11047.
Hunk #20 FAILED at 11119.
Hunk #21 FAILED at 11133.
Hunk #22 FAILED at 11196.
Hunk #23 FAILED at 11210.
Hunk #24 FAILED at 11495.
Hunk #25 succeeded at 11562 (offset -87 lines).
Hunk #26 FAILED at 11661.
18 out of 26 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
Repo: dpdk
18023:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline.c
Hunk #6 FAILED at 6611.
Hunk #7 FAILED at 6672.
Hunk #8 succeeded at 4124 with fuzz 2 (offset -2632 lines).
Hunk #9 FAILED at 6822.
Hunk #10 succeeded at 11453 with fuzz 2 (offset 4568 lines).
Hunk #11 FAILED at 6953.
Hunk #12 FAILED at 7032.
Hunk #13 FAILED at 10803.
Hunk #14 FAILED at 10857.
Hunk #15 FAILED at 10872.
Hunk #16 FAILED at 10945.
Hunk #17 FAILED at 10960.
Hunk #18 FAILED at 11033.
Hunk #19 FAILED at 11047.
Hunk #20 FAILED at 11119.
Hunk #21 FAILED at 11133.
Hunk #22 FAILED at 11196.
Hunk #23 FAILED at 11210.
Hunk #24 FAILED at 11495.
Hunk #25 succeeded at 11610 (offset -39 lines).
Hunk #26 FAILED at 11661.
18 out of 26 hunks FAILED -- saving rejects to file app/test-pmd/cmdline.c.rej
DPDK STV team
reply other threads:[~2016-12-16 6:13 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='9ddf0d$10otrmt@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=qi.z.zhang@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).