From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw26159 [PATCH v2 03/11] cryptodev: add private session size retrieval function
Date: 04 Jul 2017 03:52:17 -0700 [thread overview]
Message-ID: <e81775$12ppf80@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26159
_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:9fc7090f258bb1a5b624f8ebbec551d0017c1399
Repo:dpdk-next-crypto, Branch:master, CommitID:63088c36c19b98284e39bf040ef7ec44a16e000b
Repo:dpdk-next-net, Branch:master, CommitID:d8ee8d7efc25a5ac0c3fca765f2244955ce8adac
Repo:dpdk-next-virtio, Branch:master, CommitID:98b53e38c195c0140d1b9d5b412986f3b92cfcf3
Repo:dpdk, Branch:master, CommitID:190ce8645e1ebeb0733f9dbc7fa854b50d1dac2e
Apply patch file failed:
Repo: dpdk
26159:
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 894 (offset 38 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
Repo: dpdk-next-crypto
26159:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 succeeded at 1278 (offset 61 lines).
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 980 (offset 124 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
Repo: dpdk-next-net
26159:
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 894 (offset 38 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
Repo: dpdk-next-virtio
26159:
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 894 (offset 38 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
Repo: dpdk-next-eventdev
26159:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 succeeded at 1470 (offset 253 lines).
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 923 (offset 67 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
DPDK STV team
next reply other threads:[~2017-07-04 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 10:52 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-02 1:47 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='e81775$12ppf80@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).