From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56014[v3, 5/8] test/crypto: add zuc test cases for auth-cipher
Date: 19 Jul 2019 22:38:26 -0700 [thread overview]
Message-ID: <ee68f5$7gl3t5@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56014
_apply issues_
Submitter: Damian Nowak <damianx.nowak@intel.com>
Date: 2019-07-03 11:15:55
Reply_mail: 20190703111558.11552-6-damianx.nowak@intel.com
DPDK git baseline:
Repo:dpdk-next-crypto, CommitID: 457f6e1dbb63a7e772d67dc88a8a3a14a3fc49ee
Repo:dpdk, CommitID: c0ed103a027385f14f352d46ff5450826b2746b7
*Repo: dpdk-next-crypto
/** HMAC_MD5 Authentication */
TEST_CASE_ST(ut_setup, ut_teardown,
test_MD5_HMAC_generate_case_1),
error: patch failed: app/test/test_cryptodev.c:9480
error: app/test/test_cryptodev.c: patch does not apply
Checking patch app/test/test_cryptodev_zuc_test_vectors.h...
error: while searching for:
} validCipherLenInBits;
struct {
unsigned len;
} validAuthLenInBits;
error: patch failed: app/test/test_cryptodev_zuc_test_vectors.h:35
error: app/test/test_cryptodev_zuc_test_vectors.h: patch does not apply
*Repo: dpdk
/** HMAC_MD5 Authentication */
TEST_CASE_ST(ut_setup, ut_teardown,
test_MD5_HMAC_generate_case_1),
error: patch failed: app/test/test_cryptodev.c:9480
error: app/test/test_cryptodev.c: patch does not apply
Checking patch app/test/test_cryptodev_zuc_test_vectors.h...
error: while searching for:
} validCipherLenInBits;
struct {
unsigned len;
} validAuthLenInBits;
error: patch failed: app/test/test_cryptodev_zuc_test_vectors.h:35
error: app/test/test_cryptodev_zuc_test_vectors.h: patch does not apply
DPDK STV team
next reply other threads:[~2019-07-20 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 5:38 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 4:24 sys_stv
2019-07-04 7:49 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='ee68f5$7gl3t5@orsmga001.jf.intel.com' \
--to=sys_stv@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).