From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: zbigniew.bodek@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw19750 [PATCH v6 8/8] app/test: add ARMv8 crypto tests and test vectors
Date: 18 Jan 2017 13:48:48 -0800 [thread overview]
Message-ID: <e81775$10l47gt@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5597 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19750
_apply patch file failure_
Submitter: zbigniew.bodek@caviumnetworks.com
Date: Wed, 18 Jan 2017 21:01:55 +0100
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:22e382ec8dbb964535bd057f35fd84dc5b761dcb
Repo:dpdk-next-net, Branch:master, CommitID:2d440d30b571cffbb6faa281089c2f39c8c792e1
Apply patch file failed:
Repo: dpdk-next-crypto
19750:
patching file app/test/test_cryptodev.c
Hunk #1 succeeded at 370 (offset 22 lines).
Hunk #2 succeeded at 1653 (offset 38 lines).
Hunk #3 succeeded at 7940 (offset 55 lines).
Hunk #4 succeeded at 8028 with fuzz 1 (offset 63 lines).
Hunk #5 FAILED at 7981.
1 out of 5 hunks FAILED -- saving rejects to file app/test/test_cryptodev.c.rej
patching file app/test/test_cryptodev_aes_test_vectors.h
Hunk #1 succeeded at 917 (offset 92 lines).
Hunk #2 FAILED at 980.
Hunk #3 FAILED at 994.
Hunk #4 FAILED at 1090.
Hunk #5 FAILED at 1099.
Hunk #6 FAILED at 1142.
Hunk #7 FAILED at 1151.
6 out of 7 hunks FAILED -- saving rejects to file app/test/test_cryptodev_aes_test_vectors.h.rej
patching file app/test/test_cryptodev_blockcipher.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file app/test/test_cryptodev_blockcipher.c.rej
patching file app/test/test_cryptodev_blockcipher.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test/test_cryptodev_blockcipher.h.rej
patching file app/test/test_cryptodev_perf.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
9 out of 9 hunks ignored -- saving rejects to file app/test/test_cryptodev_perf.c.rej
Repo: dpdk-next-net
19750:
patching file app/test/test_cryptodev.c
Hunk #2 succeeded at 1567 (offset -48 lines).
Hunk #3 succeeded at 6542 (offset -1343 lines).
Hunk #4 succeeded at 6622 (offset -1343 lines).
Hunk #5 succeeded at 6638 (offset -1343 lines).
patching file app/test/test_cryptodev_aes_test_vectors.h
Hunk #2 FAILED at 980.
Hunk #3 FAILED at 994.
Hunk #4 succeeded at 1046 (offset -44 lines).
Hunk #5 succeeded at 1056 (offset -44 lines).
Hunk #6 succeeded at 1100 (offset -44 lines).
Hunk #7 succeeded at 1110 (offset -44 lines).
2 out of 7 hunks FAILED -- saving rejects to file app/test/test_cryptodev_aes_test_vectors.h.rej
patching file app/test/test_cryptodev_blockcipher.c
Hunk #1 succeeded at 82 (offset -20 lines).
Hunk #2 succeeded at 509 (offset -137 lines).
patching file app/test/test_cryptodev_blockcipher.h
Hunk #1 succeeded at 49 (offset -1 lines).
patching file app/test/test_cryptodev_perf.c
Hunk #3 succeeded at 2450 (offset -3 lines).
Hunk #4 succeeded at 2844 (offset -7 lines).
Hunk #5 succeeded at 3567 (offset -24 lines).
Hunk #6 succeeded at 4008 (offset -29 lines).
Hunk #7 succeeded at 4677 (offset -30 lines).
Hunk #8 succeeded at 4746 (offset -30 lines).
Hunk #9 succeeded at 4763 (offset -30 lines).
Repo: dpdk-next-virtio
19750:
patching file app/test/test_cryptodev.c
Hunk #2 succeeded at 1567 (offset -48 lines).
Hunk #3 succeeded at 6542 (offset -1343 lines).
Hunk #4 succeeded at 6622 (offset -1343 lines).
Hunk #5 succeeded at 6638 (offset -1343 lines).
patching file app/test/test_cryptodev_aes_test_vectors.h
Hunk #2 FAILED at 980.
Hunk #3 FAILED at 994.
Hunk #4 succeeded at 1046 (offset -44 lines).
Hunk #5 succeeded at 1056 (offset -44 lines).
Hunk #6 succeeded at 1100 (offset -44 lines).
Hunk #7 succeeded at 1110 (offset -44 lines).
2 out of 7 hunks FAILED -- saving rejects to file app/test/test_cryptodev_aes_test_vectors.h.rej
patching file app/test/test_cryptodev_blockcipher.c
Hunk #1 succeeded at 82 (offset -20 lines).
Hunk #2 succeeded at 509 (offset -137 lines).
patching file app/test/test_cryptodev_blockcipher.h
Hunk #1 succeeded at 49 (offset -1 lines).
patching file app/test/test_cryptodev_perf.c
Hunk #3 succeeded at 2450 (offset -3 lines).
Hunk #4 succeeded at 2844 (offset -7 lines).
Hunk #5 succeeded at 3567 (offset -24 lines).
Hunk #6 succeeded at 4008 (offset -29 lines).
Hunk #7 succeeded at 4677 (offset -30 lines).
Hunk #8 succeeded at 4746 (offset -30 lines).
Hunk #9 succeeded at 4763 (offset -30 lines).
Repo: dpdk
19750:
patching file app/test/test_cryptodev.c
Hunk #2 succeeded at 1567 (offset -48 lines).
Hunk #3 succeeded at 6542 (offset -1343 lines).
Hunk #4 succeeded at 6622 (offset -1343 lines).
Hunk #5 succeeded at 6638 (offset -1343 lines).
patching file app/test/test_cryptodev_aes_test_vectors.h
Hunk #2 FAILED at 980.
Hunk #3 FAILED at 994.
Hunk #4 succeeded at 1046 (offset -44 lines).
Hunk #5 succeeded at 1056 (offset -44 lines).
Hunk #6 succeeded at 1100 (offset -44 lines).
Hunk #7 succeeded at 1110 (offset -44 lines).
2 out of 7 hunks FAILED -- saving rejects to file app/test/test_cryptodev_aes_test_vectors.h.rej
patching file app/test/test_cryptodev_blockcipher.c
Hunk #1 succeeded at 82 (offset -20 lines).
Hunk #2 succeeded at 509 (offset -137 lines).
patching file app/test/test_cryptodev_blockcipher.h
Hunk #1 succeeded at 49 (offset -1 lines).
patching file app/test/test_cryptodev_perf.c
Hunk #3 succeeded at 2450 (offset -3 lines).
Hunk #4 succeeded at 2844 (offset -7 lines).
Hunk #5 succeeded at 3567 (offset -24 lines).
Hunk #6 succeeded at 4008 (offset -29 lines).
Hunk #7 succeeded at 4677 (offset -30 lines).
Hunk #8 succeeded at 4746 (offset -30 lines).
Hunk #9 succeeded at 4763 (offset -30 lines).
DPDK STV team
reply other threads:[~2017-01-18 21:48 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$10l47gt@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=zbigniew.bodek@caviumnetworks.com \
/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).