From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw18088 [PATCH v2 05/25] cmdline: add alignment constraint
Date: 16 Dec 2016 19:34:25 -0800 [thread overview]
Message-ID: <6f050a$108ocho@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/18088
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Fri, 16 Dec 2016 17:25:02 +0100
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:ee103f0ee24a8f2f2243f128796608028fc8ef4d
Repo:dpdk-next-net, Branch:master, CommitID:f4fa617532e5ffa71f0cedc9f37fda069c8eb856
Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
Repo:dpdk, Branch:master, CommitID:c431384c8fbf8503693bcae1bdcd58d6fa459b8a
Apply patch file failed:
Repo: dpdk-next-crypto
18088:
patching file lib/librte_cmdline/cmdline_parse.c
Hunk #1 FAILED at 255.
Hunk #2 FAILED at 318.
Hunk #3 succeeded at 333 (offset -20 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_cmdline/cmdline_parse.c.rej
Repo: dpdk-next-net
18088:
patching file lib/librte_cmdline/cmdline_parse.c
Hunk #1 FAILED at 255.
Hunk #2 FAILED at 318.
Hunk #3 succeeded at 333 (offset -20 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_cmdline/cmdline_parse.c.rej
Repo: dpdk-next-virtio
18088:
patching file lib/librte_cmdline/cmdline_parse.c
Hunk #1 FAILED at 255.
Hunk #2 FAILED at 318.
Hunk #3 succeeded at 333 (offset -20 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_cmdline/cmdline_parse.c.rej
Repo: dpdk
18088:
patching file lib/librte_cmdline/cmdline_parse.c
Hunk #1 FAILED at 255.
Hunk #2 FAILED at 318.
Hunk #3 succeeded at 333 (offset -20 lines).
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_cmdline/cmdline_parse.c.rej
DPDK STV team
reply other threads:[~2016-12-17 3:34 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='6f050a$108ocho@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@6wind.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).