From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw26164 [PATCH v2 08/11] cryptodev: remove mempool from session
Date: 01 Jul 2017 19:15:41 -0700 [thread overview]
Message-ID: <ffb989$356s2l@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3808 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26164
_apply patch file failure_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Fri, 30 Jun 2017 18:09:25 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:64f889f8e6f978412100acd36728bfe43cf00359
Repo:dpdk-next-crypto, Branch:master, CommitID:35b8eaf651395d4f869f50199594191970d8b7ca
Repo:dpdk-next-net, Branch:master, CommitID:143c03925695511f1bb692644982f643c0ede9bd
Repo:dpdk-next-virtio, Branch:master, CommitID:f7ab905f26f4e6cb2fe19ca1160527de918fdbb6
Repo:dpdk, Branch:master, CommitID:da8e7a3086b263972cda1e41ddd2078855842008
Apply patch file failed:
Repo: dpdk
26164:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 797.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-crypto
26164:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 797.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-net
26164:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 797.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-virtio
26164:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 797.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-eventdev
26164:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 797.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
DPDK STV team
next reply other threads:[~2017-07-02 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 2:15 sys_stv [this message]
2017-07-04 11:03 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='ffb989$356s2l@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=pablo.de.lara.guarch@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).