automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jianjay.zhou@huawei.com
Subject: [dpdk-test-report] |FAILURE| pw38157 [PATCH v10 09/10] test/crypto: add function tests for virtio crypto PMD
Date: 26 Apr 2018 14:19:40 -0700	[thread overview]
Message-ID: <ca5293$1fu3dq@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Jay Zhou <jianjay.zhou@huawei.com>
Date: Mon, 16 Apr 2018 10:21:23 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
                   Repo:dpdk-next-net, Branch:master, CommitID:e657a5d5fae02bcd8e62d4e57338d7d363e638c1
                   Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
                   Repo:dpdk, Branch:master, CommitID:09f4aa2b955f9f9e2e662ca7c5f3fa7258ef4614
                   
Apply patch file failed:
Repo: dpdk
38157:
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 1839 (offset 19 lines).
Hunk #2 succeeded at 8929 (offset 31 lines).
Hunk #3 succeeded at 9886 (offset 47 lines).
Hunk #4 FAILED at 10087.
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev.c.rej
patching file test/test/test_cryptodev.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 test/test/test_cryptodev.h.rej
patching file test/test/test_cryptodev_aes_test_vectors.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
8 out of 8 hunks ignored -- saving rejects to file test/test/test_cryptodev_aes_test_vectors.h.rej
patching file test/test/test_cryptodev_blockcipher.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file test/test/test_cryptodev_blockcipher.c.rej
patching file test/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 test/test/test_cryptodev_blockcipher.h.rej

Repo: dpdk-next-crypto
38157:
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 1839 (offset 19 lines).
Hunk #2 succeeded at 8929 (offset 31 lines).
Hunk #3 succeeded at 9886 (offset 47 lines).
Hunk #4 FAILED at 10087.
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev.c.rej
patching file test/test/test_cryptodev.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 test/test/test_cryptodev.h.rej
patching file test/test/test_cryptodev_aes_test_vectors.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
8 out of 8 hunks ignored -- saving rejects to file test/test/test_cryptodev_aes_test_vectors.h.rej
patching file test/test/test_cryptodev_blockcipher.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file test/test/test_cryptodev_blockcipher.c.rej
patching file test/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 test/test/test_cryptodev_blockcipher.h.rej

Repo: dpdk-next-net
38157:
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 1839 (offset 19 lines).
Hunk #2 succeeded at 8929 (offset 31 lines).
Hunk #3 succeeded at 9886 (offset 47 lines).
Hunk #4 FAILED at 10087.
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev.c.rej
patching file test/test/test_cryptodev.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 test/test/test_cryptodev.h.rej
patching file test/test/test_cryptodev_aes_test_vectors.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
8 out of 8 hunks ignored -- saving rejects to file test/test/test_cryptodev_aes_test_vectors.h.rej
patching file test/test/test_cryptodev_blockcipher.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file test/test/test_cryptodev_blockcipher.c.rej
patching file test/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 test/test/test_cryptodev_blockcipher.h.rej

Repo: dpdk-next-virtio
38157:
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 1765 (offset -55 lines).
Hunk #2 succeeded at 8786 (offset -112 lines).
Hunk #3 succeeded at 9695 (offset -144 lines).
Hunk #4 FAILED at 10087.
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev.c.rej
patching file test/test/test_cryptodev.h
Hunk #1 FAILED at 63.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test_cryptodev.h.rej
patching file test/test/test_cryptodev_aes_test_vectors.h
Hunk #1 FAILED at 1544.
Hunk #2 FAILED at 1557.
Hunk #3 FAILED at 1569.
Hunk #4 FAILED at 1591.
Hunk #5 FAILED at 1612.
Hunk #6 FAILED at 1625.
Hunk #7 FAILED at 1636.
Hunk #8 FAILED at 1647.
8 out of 8 hunks FAILED -- saving rejects to file test/test/test_cryptodev_aes_test_vectors.h.rej
patching file test/test/test_cryptodev_blockcipher.c
Hunk #1 succeeded at 68 (offset -2 lines).
Hunk #2 FAILED at 99.
Hunk #3 succeeded at 571 (offset -5 lines).
Hunk #4 succeeded at 635 (offset -7 lines).
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev_blockcipher.c.rej
patching file test/test/test_cryptodev_blockcipher.h
Hunk #1 FAILED at 28.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test_cryptodev_blockcipher.h.rej

Repo: dpdk-next-eventdev
38157:
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 1765 (offset -55 lines).
Hunk #2 succeeded at 8786 (offset -112 lines).
Hunk #3 succeeded at 9695 (offset -144 lines).
Hunk #4 FAILED at 10087.
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev.c.rej
patching file test/test/test_cryptodev.h
Hunk #1 FAILED at 63.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test_cryptodev.h.rej
patching file test/test/test_cryptodev_aes_test_vectors.h
Hunk #1 FAILED at 1544.
Hunk #2 FAILED at 1557.
Hunk #3 FAILED at 1569.
Hunk #4 FAILED at 1591.
Hunk #5 FAILED at 1612.
Hunk #6 FAILED at 1625.
Hunk #7 FAILED at 1636.
Hunk #8 FAILED at 1647.
8 out of 8 hunks FAILED -- saving rejects to file test/test/test_cryptodev_aes_test_vectors.h.rej
patching file test/test/test_cryptodev_blockcipher.c
Hunk #1 succeeded at 68 (offset -2 lines).
Hunk #2 FAILED at 99.
Hunk #3 succeeded at 571 (offset -5 lines).
Hunk #4 succeeded at 635 (offset -7 lines).
1 out of 4 hunks FAILED -- saving rejects to file test/test/test_cryptodev_blockcipher.c.rej
patching file test/test/test_cryptodev_blockcipher.h
Hunk #1 FAILED at 28.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test_cryptodev_blockcipher.h.rej


DPDK STV team

                 reply	other threads:[~2018-04-26 21:19 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='ca5293$1fu3dq@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=jianjay.zhou@huawei.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).