From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: akhil.goyal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw29838 [PATCH v3 05/12] mbuf: add security crypto flags and mbuf fields
Date: 11 Oct 2017 02:10:32 -0700 [thread overview]
Message-ID: <7327ef$4aeqf3@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3454 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29838
_apply patch file failure_
Submitter: Akhil Goyal <akhil.goyal@nxp.com>
Date: Fri, 6 Oct 2017 23:41:41 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
Repo:dpdk-next-crypto, Branch:master, CommitID:f255b48dc3e66ca94c5bd60ce20f68ba0eb7f33e
Repo:dpdk-next-net, Branch:master, CommitID:1b2a708972a81acb6f8459fcce1b4cd8217e7c15
Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
Repo:dpdk, Branch:master, CommitID:fc8030eb8fe996534b5c6c873ea7f56ad407415e
Apply patch file failed:
Repo: dpdk
29838:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 324 (offset 1 line).
Hunk #2 succeeded at 361 (offset 1 line).
Hunk #3 succeeded at 415 (offset 1 line).
Hunk #4 succeeded at 449 (offset 1 line).
patching file lib/librte_mbuf/rte_mbuf.h
patching file lib/librte_mbuf/rte_mbuf_ptype.c
Hunk #1 FAILED at 89.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_ptype.c.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.h
Hunk #1 succeeded at 415 with fuzz 2 (offset 32 lines).
Repo: dpdk-next-crypto
29838:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 324 (offset 1 line).
Hunk #2 succeeded at 361 (offset 1 line).
Hunk #3 succeeded at 415 (offset 1 line).
Hunk #4 succeeded at 449 (offset 1 line).
patching file lib/librte_mbuf/rte_mbuf.h
patching file lib/librte_mbuf/rte_mbuf_ptype.c
Hunk #1 FAILED at 89.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_ptype.c.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.h
Hunk #1 succeeded at 415 with fuzz 2 (offset 32 lines).
Repo: dpdk-next-net
29838:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 324 (offset 1 line).
Hunk #2 succeeded at 361 (offset 1 line).
Hunk #3 succeeded at 415 (offset 1 line).
Hunk #4 succeeded at 449 (offset 1 line).
patching file lib/librte_mbuf/rte_mbuf.h
patching file lib/librte_mbuf/rte_mbuf_ptype.c
Hunk #1 FAILED at 89.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_ptype.c.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.h
Hunk #1 succeeded at 415 with fuzz 2 (offset 32 lines).
Repo: dpdk-next-virtio
29838:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 324 (offset 1 line).
Hunk #2 succeeded at 361 (offset 1 line).
Hunk #3 succeeded at 415 (offset 1 line).
Hunk #4 succeeded at 449 (offset 1 line).
patching file lib/librte_mbuf/rte_mbuf.h
patching file lib/librte_mbuf/rte_mbuf_ptype.c
Hunk #1 FAILED at 89.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_ptype.c.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.h
Hunk #1 succeeded at 415 with fuzz 2 (offset 32 lines).
Repo: dpdk-next-eventdev
29838:
patching file lib/librte_mbuf/rte_mbuf.c
Hunk #1 succeeded at 324 (offset 1 line).
Hunk #2 succeeded at 361 (offset 1 line).
Hunk #3 succeeded at 415 (offset 1 line).
Hunk #4 succeeded at 449 (offset 1 line).
patching file lib/librte_mbuf/rte_mbuf.h
patching file lib/librte_mbuf/rte_mbuf_ptype.c
Hunk #1 FAILED at 89.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_mbuf/rte_mbuf_ptype.c.rej
patching file lib/librte_mbuf/rte_mbuf_ptype.h
Hunk #1 succeeded at 415 with fuzz 2 (offset 32 lines).
DPDK STV team
reply other threads:[~2017-10-11 9:10 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='7327ef$4aeqf3@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=akhil.goyal@nxp.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).