[dpdk-test-report] |FAILURE| pw27988 [PATCH RFC 3/5] rte_security: updates and enabled security operations for ethdev

automatic DPDK test reports
 help / color / mirror / Atom feed

From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: radu.nicolau@intel.com
Subject: [dpdk-test-report] |FAILURE| pw27988 [PATCH RFC 3/5] rte_security: updates and enabled security operations for ethdev
Date: 25 Aug 2017 09:59:29 -0700	[thread overview]
Message-ID: <1a8a4b$13d3rrp@fmsmga001.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 6964 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27988

_apply patch file failure_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Fri, 25 Aug 2017 15:57:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-crypto, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-net, Branch:master, CommitID:729fab783ca0b6a44281112285d58250b459ba09
                   Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
                   Repo:dpdk, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   
Apply patch file failed:
Repo: dpdk
27988:
patching file lib/Makefile
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #1 FAILED at 371.
Hunk #2 FAILED at 382.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_pmd.h.rej
patching file lib/librte_cryptodev/rte_cryptodev_version.map
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.c b/lib/librte_cryptodev/rte_security.c
|index 7c73c93..5f35355 100644
|--- a/lib/librte_cryptodev/rte_security.c
|+++ b/lib/librte_cryptodev/rte_security.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 124
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.h b/lib/librte_cryptodev/rte_security.h
|index 9747d5e..0c8b358 100644
|--- a/lib/librte_cryptodev/rte_security.h
|+++ b/lib/librte_cryptodev/rte_security.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-crypto
27988:
patching file lib/Makefile
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #1 FAILED at 371.
Hunk #2 FAILED at 382.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_pmd.h.rej
patching file lib/librte_cryptodev/rte_cryptodev_version.map
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.c b/lib/librte_cryptodev/rte_security.c
|index 7c73c93..5f35355 100644
|--- a/lib/librte_cryptodev/rte_security.c
|+++ b/lib/librte_cryptodev/rte_security.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 124
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.h b/lib/librte_cryptodev/rte_security.h
|index 9747d5e..0c8b358 100644
|--- a/lib/librte_cryptodev/rte_security.h
|+++ b/lib/librte_cryptodev/rte_security.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-net
27988:
patching file lib/Makefile
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #1 FAILED at 371.
Hunk #2 FAILED at 382.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_pmd.h.rej
patching file lib/librte_cryptodev/rte_cryptodev_version.map
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.c b/lib/librte_cryptodev/rte_security.c
|index 7c73c93..5f35355 100644
|--- a/lib/librte_cryptodev/rte_security.c
|+++ b/lib/librte_cryptodev/rte_security.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 124
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.h b/lib/librte_cryptodev/rte_security.h
|index 9747d5e..0c8b358 100644
|--- a/lib/librte_cryptodev/rte_security.h
|+++ b/lib/librte_cryptodev/rte_security.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-virtio
27988:
patching file lib/Makefile
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #1 FAILED at 371.
Hunk #2 FAILED at 382.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_pmd.h.rej
patching file lib/librte_cryptodev/rte_cryptodev_version.map
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.c b/lib/librte_cryptodev/rte_security.c
|index 7c73c93..5f35355 100644
|--- a/lib/librte_cryptodev/rte_security.c
|+++ b/lib/librte_cryptodev/rte_security.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 124
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.h b/lib/librte_cryptodev/rte_security.h
|index 9747d5e..0c8b358 100644
|--- a/lib/librte_cryptodev/rte_security.h
|+++ b/lib/librte_cryptodev/rte_security.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-eventdev
27988:
patching file lib/Makefile
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #1 FAILED at 371.
Hunk #2 FAILED at 382.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_pmd.h.rej
patching file lib/librte_cryptodev/rte_cryptodev_version.map
can't find file to patch at input line 57
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.c b/lib/librte_cryptodev/rte_security.c
|index 7c73c93..5f35355 100644
|--- a/lib/librte_cryptodev/rte_security.c
|+++ b/lib/librte_cryptodev/rte_security.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 124
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_cryptodev/rte_security.h b/lib/librte_cryptodev/rte_security.h
|index 9747d5e..0c8b358 100644
|--- a/lib/librte_cryptodev/rte_security.h
|+++ b/lib/librte_cryptodev/rte_security.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored


DPDK STV team

                 reply	other threads:[~2017-08-25 16:59 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='1a8a4b$13d3rrp@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=radu.nicolau@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).