From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: abhinandan.gujjar@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37077 [PATCH dpdk-dev v1 2/5] eventdev: add crypto adapter implementation
Date: 11 Apr 2018 18:21:42 -0700 [thread overview]
Message-ID: <ca5293$1c2jvj@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3325 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37077
_apply patch file failure_
Submitter: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Date: Wed, 4 Apr 2018 12:26:39 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:8cafb78bb4d7a724c41aefc326d9eae79c6fb6e7
Repo:dpdk-next-crypto, Branch:master, CommitID:38193ec5c89ecb0f3fd5b25acd06a855ba7537c9
Repo:dpdk-next-net, Branch:master, CommitID:46401b5cde16f1c918e1160e837c51f35976a35e
Repo:dpdk-next-virtio, Branch:master, CommitID:82a2474236daa8730dd047fa70884b2b9d130aec
Repo:dpdk, Branch:master, CommitID:b3ec974c344c0528f34e475584ad3ea0f219fa85
Apply patch file failed:
Repo: dpdk
37077:
patching file config/common_base
Hunk #1 succeeded at 557 (offset 7 lines).
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_event_crypto_adapter.c
patching file lib/librte_eventdev/rte_event_crypto_adapter.h
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 79.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-crypto
37077:
patching file config/common_base
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_event_crypto_adapter.c
patching file lib/librte_eventdev/rte_event_crypto_adapter.h
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 79.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-net
37077:
patching file config/common_base
Hunk #1 succeeded at 563 (offset 13 lines).
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_event_crypto_adapter.c
patching file lib/librte_eventdev/rte_event_crypto_adapter.h
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 79.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-virtio
37077:
patching file config/common_base
Hunk #1 succeeded at 544 (offset -6 lines).
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_event_crypto_adapter.c
patching file lib/librte_eventdev/rte_event_crypto_adapter.h
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 79.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-eventdev
37077:
patching file config/common_base
Hunk #1 FAILED at 550.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file lib/Makefile
Hunk #1 FAILED at 31.
1 out of 1 hunk FAILED -- saving rejects to file lib/Makefile.rej
patching file lib/librte_eventdev/Makefile
Hunk #1 FAILED at 15.
Hunk #2 FAILED at 28.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eventdev/Makefile.rej
patching file lib/librte_eventdev/rte_event_crypto_adapter.c
patching file lib/librte_eventdev/rte_event_crypto_adapter.h
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 succeeded at 78 with fuzz 2 (offset -1 lines).
DPDK STV team
reply other threads:[~2018-04-12 1:21 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='ca5293$1c2jvj@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=abhinandan.gujjar@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).