automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25593 [PATCH 16/22] cryptodev: remove AAD length from crypto op
Date: 29 Jun 2017 20:01:14 -0700	[thread overview]
Message-ID: <ffb989$34hvg3@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Wed, 21 Jun 2017 08:47:14 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
                   Repo:dpdk-next-crypto, Branch:master, CommitID:c7a7050f3b389ef895b7ffa4ef2467e0da6fd67b
                   Repo:dpdk-next-net, Branch:master, CommitID:8497b7cf95e4654afc97fc4714151649f04e0e58
                   Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
                   Repo:dpdk, Branch:master, CommitID:bbe569daa7e99b36d44b12bb3d23ddfbc26d383c
                   
Apply patch file failed:
Repo: dpdk-next-net
25593:
patching file app/test-crypto-perf/cperf_ops.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
patching file drivers/crypto/openssl/rte_openssl_pmd.c
patching file drivers/crypto/openssl/rte_openssl_pmd_private.h
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
patching file drivers/crypto/qat/qat_crypto.c
patching file examples/ipsec-secgw/esp.c
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_crypto_sym.h
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 4674 (offset 36 lines).
Hunk #2 succeeded at 4788 (offset 36 lines).
Hunk #3 succeeded at 6351 (offset 36 lines).
Hunk #4 succeeded at 6415 (offset 36 lines).
Hunk #5 succeeded at 6895 (offset 36 lines).
Hunk #6 succeeded at 7228 (offset 36 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #4 succeeded at 2826 (offset 46 lines).
Hunk #5 FAILED at 2857.
Hunk #6 succeeded at 2940 (offset 50 lines).
Hunk #7 FAILED at 2933.
Hunk #8 succeeded at 3054 (offset 54 lines).
Hunk #9 succeeded at 4193 (offset 54 lines).
Hunk #10 succeeded at 4229 (offset 54 lines).
Hunk #11 succeeded at 4246 (offset 54 lines).
Hunk #12 succeeded at 4264 (offset 54 lines).
Hunk #13 succeeded at 4400 (offset 54 lines).
Hunk #14 succeeded at 4479 (offset 54 lines).
2 out of 14 hunks FAILED -- saving rejects to file test/test/test_cryptodev_perf.c.rej

Repo: dpdk-next-virtio
25593:
patching file app/test-crypto-perf/cperf_ops.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
patching file drivers/crypto/openssl/rte_openssl_pmd.c
patching file drivers/crypto/openssl/rte_openssl_pmd_private.h
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
patching file drivers/crypto/qat/qat_crypto.c
patching file examples/ipsec-secgw/esp.c
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_crypto_sym.h
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 4674 (offset 36 lines).
Hunk #2 succeeded at 4788 (offset 36 lines).
Hunk #3 succeeded at 6351 (offset 36 lines).
Hunk #4 succeeded at 6415 (offset 36 lines).
Hunk #5 succeeded at 6895 (offset 36 lines).
Hunk #6 succeeded at 7228 (offset 36 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #4 succeeded at 2826 (offset 46 lines).
Hunk #5 FAILED at 2857.
Hunk #6 succeeded at 2940 (offset 50 lines).
Hunk #7 FAILED at 2933.
Hunk #8 succeeded at 3054 (offset 54 lines).
Hunk #9 succeeded at 4193 (offset 54 lines).
Hunk #10 succeeded at 4229 (offset 54 lines).
Hunk #11 succeeded at 4246 (offset 54 lines).
Hunk #12 succeeded at 4264 (offset 54 lines).
Hunk #13 succeeded at 4400 (offset 54 lines).
Hunk #14 succeeded at 4479 (offset 54 lines).
2 out of 14 hunks FAILED -- saving rejects to file test/test/test_cryptodev_perf.c.rej

Repo: dpdk-next-eventdev
25593:
patching file app/test-crypto-perf/cperf_ops.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
patching file drivers/crypto/openssl/rte_openssl_pmd.c
patching file drivers/crypto/openssl/rte_openssl_pmd_private.h
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
patching file drivers/crypto/qat/qat_crypto.c
patching file examples/ipsec-secgw/esp.c
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_crypto_sym.h
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 4674 (offset 36 lines).
Hunk #2 succeeded at 4788 (offset 36 lines).
Hunk #3 succeeded at 6351 (offset 36 lines).
Hunk #4 succeeded at 6415 (offset 36 lines).
Hunk #5 succeeded at 6895 (offset 36 lines).
Hunk #6 succeeded at 7228 (offset 36 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #4 succeeded at 2826 (offset 46 lines).
Hunk #5 FAILED at 2857.
Hunk #6 succeeded at 2940 (offset 50 lines).
Hunk #7 FAILED at 2933.
Hunk #8 succeeded at 3054 (offset 54 lines).
Hunk #9 succeeded at 4193 (offset 54 lines).
Hunk #10 succeeded at 4229 (offset 54 lines).
Hunk #11 succeeded at 4246 (offset 54 lines).
Hunk #12 succeeded at 4264 (offset 54 lines).
Hunk #13 succeeded at 4400 (offset 54 lines).
Hunk #14 succeeded at 4479 (offset 54 lines).
2 out of 14 hunks FAILED -- saving rejects to file test/test/test_cryptodev_perf.c.rej


DPDK STV team

             reply	other threads:[~2017-06-30  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  3:01 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-23 16:58 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='ffb989$34hvg3@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=pablo.de.lara.guarch@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).