From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw26498 [PATCH v4 06/12] cryptodev: remove device id from crypto session
Date: 06 Jul 2017 21:01:29 -0700 [thread overview]
Message-ID: <e81775$12re8p9@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3413 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26498
_apply patch file failure_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Wed, 5 Jul 2017 06:26:13 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:9fc7090f258bb1a5b624f8ebbec551d0017c1399
Repo:dpdk-next-crypto, Branch:master, CommitID:324377c6f82a9274a489f3a31e1d1feef9a29aed
Repo:dpdk-next-net, Branch:master, CommitID:fe6ffaf83cf9e2130ddda2fc6f6b5cbc9176f27b
Repo:dpdk-next-virtio, Branch:master, CommitID:98b53e38c195c0140d1b9d5b412986f3b92cfcf3
Repo:dpdk, Branch:master, CommitID:cfea1f3048d1bfda61036e6f823949fba4d692d4
Apply patch file failed:
Repo: dpdk
26498:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 208.
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
Hunk #1 FAILED at 1087.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 884.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-crypto
26498:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 208.
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
Hunk #1 FAILED at 1087.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 884.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-net
26498:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 208.
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
Hunk #1 FAILED at 1087.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 884.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-virtio
26498:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 208.
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
Hunk #1 FAILED at 1087.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 884.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
Repo: dpdk-next-eventdev
26498:
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 208.
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
Hunk #1 FAILED at 1087.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 FAILED at 884.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.h.rej
DPDK STV team
reply other threads:[~2017-07-07 4:01 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$12re8p9@fmsmga001.fm.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).