From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: borisp@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw26693 [PATCH RFC 4/7] cryptodev: add ipsec xform
Date: 10 Jul 2017 01:33:04 -0700 [thread overview]
Message-ID: <e81775$12sckve@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26693
_apply patch file failure_
Submitter: Boris Pismenny <borisp@mellanox.com>
Date: Mon, 10 Jul 2017 10:35:12 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:bdd7083174143897e237050dddb069fae7219e56
Repo:dpdk-next-net, Branch:master, CommitID:b3d4e665ed3db9fb21ba016a28294245d578e012
Repo:dpdk-next-virtio, Branch:master, CommitID:42003749105c3bbd7a9e2664263d89e502665cbe
Repo:dpdk, Branch:master, CommitID:c553139afa10ebb0cde109aa26d1f8d4ab83d17d
Apply patch file failed:
Repo: dpdk
26693:
patching file lib/librte_cryptodev/rte_crypto_sym.h
Hunk #1 FAILED at 346.
Hunk #2 FAILED at 373.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_crypto_sym.h.rej
Repo: dpdk-next-crypto
26693:
patching file lib/librte_cryptodev/rte_crypto_sym.h
Hunk #1 FAILED at 346.
Hunk #2 FAILED at 373.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_crypto_sym.h.rej
Repo: dpdk-next-net
26693:
patching file lib/librte_cryptodev/rte_crypto_sym.h
Hunk #1 FAILED at 346.
Hunk #2 FAILED at 373.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_crypto_sym.h.rej
Repo: dpdk-next-virtio
26693:
patching file lib/librte_cryptodev/rte_crypto_sym.h
Hunk #1 FAILED at 346.
Hunk #2 FAILED at 373.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_crypto_sym.h.rej
DPDK STV team
reply other threads:[~2017-07-10 8:33 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$12sckve@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=borisp@mellanox.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).