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| pw26321 [PATCH v3 1/4] crypto/aesni_gcm: migrate to Multi-buffer library
Date: 05 Jul 2017 12:15:37 -0700	[thread overview]
Message-ID: <e81775$12qa5m1@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Tue,  4 Jul 2017 01:12:40 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:9fc7090f258bb1a5b624f8ebbec551d0017c1399
                   Repo:dpdk-next-crypto, Branch:master, CommitID:90c21ceb6a1040bbc9ca611d0829987f2978225d
                   Repo:dpdk-next-net, Branch:master, CommitID:cb6294fdc3fced7c12219bae0ea8e62f02199aa1
                   Repo:dpdk-next-virtio, Branch:master, CommitID:98b53e38c195c0140d1b9d5b412986f3b92cfcf3
                   Repo:dpdk, Branch:master, CommitID:a3a2e2c8f7de433e10b1548df65b20bf10086d9c
                   
Apply patch file failed:
Repo: dpdk
26321:
patching file devtools/test-build.sh
patching file doc/guides/cryptodevs/aesni_gcm.rst
patching file doc/guides/cryptodevs/features/aesni_gcm.ini
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 succeeded at 95 with fuzz 2 (offset 4 lines).
patching file drivers/crypto/aesni_gcm/Makefile
patching file drivers/crypto/aesni_gcm/aesni_gcm_ops.h
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
Hunk #2 FAILED at 119.
Hunk #3 FAILED at 167.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 253.
Hunk #6 FAILED at 272.
Hunk #7 FAILED at 291.
Hunk #8 FAILED at 310.
Hunk #9 FAILED at 337.
Hunk #10 FAILED at 442.
Hunk #11 succeeded at 413 (offset -68 lines).
Hunk #12 succeeded at 425 (offset -68 lines).
Hunk #13 succeeded at 457 (offset -68 lines).
9 out of 13 hunks FAILED -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
Hunk #2 succeeded at 74 (offset -1 lines).
Hunk #3 succeeded at 247 (offset 14 lines).
Hunk #4 succeeded at 265 (offset 14 lines).
Hunk #5 succeeded at 317 (offset 14 lines).
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
Hunk #3 succeeded at 89 with fuzz 1 (offset -2 lines).
Hunk #4 succeeded at 95 (offset -11 lines).
Hunk #5 succeeded at 110 (offset -11 lines).
patching file mk/rte.app.mk

Repo: dpdk-next-crypto
26321:
patching file devtools/test-build.sh
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file devtools/test-build.sh.rej
patching file doc/guides/cryptodevs/aesni_gcm.rst
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file doc/guides/cryptodevs/aesni_gcm.rst.rej
patching file doc/guides/cryptodevs/features/aesni_gcm.ini
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file doc/guides/cryptodevs/features/aesni_gcm.ini.rej
patching file doc/guides/rel_notes/release_17_08.rst
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/aesni_gcm/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/crypto/aesni_gcm/Makefile.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_ops.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_ops.h.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
Hunk #1 FAILED at 43.
Hunk #2 FAILED at 145.
Hunk #3 FAILED at 193.
Hunk #4 FAILED at 214.
Hunk #5 FAILED at 279.
Hunk #6 FAILED at 298.
Hunk #7 FAILED at 317.
Hunk #8 FAILED at 336.
Hunk #9 FAILED at 363.
Hunk #10 FAILED at 468.
Hunk #11 FAILED at 507.
Hunk #12 succeeded at 514 with fuzz 2 (offset -4 lines).
Hunk #13 FAILED at 550.
12 out of 13 hunks FAILED -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
5 out of 5 hunks ignored -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
5 out of 5 hunks ignored -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h.rej
patching file mk/rte.app.mk
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-net
26321:
patching file devtools/test-build.sh
patching file doc/guides/cryptodevs/aesni_gcm.rst
patching file doc/guides/cryptodevs/features/aesni_gcm.ini
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 succeeded at 85 with fuzz 2 (offset -6 lines).
patching file drivers/crypto/aesni_gcm/Makefile
patching file drivers/crypto/aesni_gcm/aesni_gcm_ops.h
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
Hunk #2 FAILED at 119.
Hunk #3 FAILED at 167.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 253.
Hunk #6 FAILED at 272.
Hunk #7 FAILED at 291.
Hunk #8 FAILED at 310.
Hunk #9 FAILED at 337.
Hunk #10 FAILED at 442.
Hunk #11 succeeded at 413 (offset -68 lines).
Hunk #12 succeeded at 425 (offset -68 lines).
Hunk #13 succeeded at 457 (offset -68 lines).
9 out of 13 hunks FAILED -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
Hunk #2 succeeded at 74 (offset -1 lines).
Hunk #3 succeeded at 247 (offset 14 lines).
Hunk #4 succeeded at 265 (offset 14 lines).
Hunk #5 succeeded at 317 (offset 14 lines).
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
Hunk #3 succeeded at 89 with fuzz 1 (offset -2 lines).
Hunk #4 succeeded at 95 (offset -11 lines).
Hunk #5 succeeded at 110 (offset -11 lines).
patching file mk/rte.app.mk

Repo: dpdk-next-virtio
26321:
patching file devtools/test-build.sh
patching file doc/guides/cryptodevs/aesni_gcm.rst
patching file doc/guides/cryptodevs/features/aesni_gcm.ini
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 succeeded at 95 with fuzz 2 (offset 4 lines).
patching file drivers/crypto/aesni_gcm/Makefile
patching file drivers/crypto/aesni_gcm/aesni_gcm_ops.h
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
Hunk #2 FAILED at 119.
Hunk #3 FAILED at 167.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 253.
Hunk #6 FAILED at 272.
Hunk #7 FAILED at 291.
Hunk #8 FAILED at 310.
Hunk #9 FAILED at 337.
Hunk #10 FAILED at 442.
Hunk #11 succeeded at 413 (offset -68 lines).
Hunk #12 succeeded at 425 (offset -68 lines).
Hunk #13 succeeded at 457 (offset -68 lines).
9 out of 13 hunks FAILED -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
Hunk #2 succeeded at 74 (offset -1 lines).
Hunk #3 succeeded at 247 (offset 14 lines).
Hunk #4 succeeded at 265 (offset 14 lines).
Hunk #5 succeeded at 317 (offset 14 lines).
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
Hunk #3 succeeded at 89 with fuzz 1 (offset -2 lines).
Hunk #4 succeeded at 95 (offset -11 lines).
Hunk #5 succeeded at 110 (offset -11 lines).
patching file mk/rte.app.mk

Repo: dpdk-next-eventdev
26321:
patching file devtools/test-build.sh
Hunk #1 succeeded at 38 with fuzz 1.
patching file doc/guides/cryptodevs/aesni_gcm.rst
patching file doc/guides/cryptodevs/features/aesni_gcm.ini
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 succeeded at 95 with fuzz 2 (offset 4 lines).
patching file drivers/crypto/aesni_gcm/Makefile
patching file drivers/crypto/aesni_gcm/aesni_gcm_ops.h
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
Hunk #1 succeeded at 42 (offset -1 lines).
Hunk #2 FAILED at 119.
Hunk #3 FAILED at 167.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 253.
Hunk #6 FAILED at 272.
Hunk #7 FAILED at 291.
Hunk #8 FAILED at 310.
Hunk #9 FAILED at 337.
Hunk #10 FAILED at 442.
Hunk #11 succeeded at 412 (offset -69 lines).
Hunk #12 FAILED at 493.
Hunk #13 succeeded at 443 (offset -70 lines).
10 out of 13 hunks FAILED -- saving rejects to file drivers/crypto/aesni_gcm/aesni_gcm_pmd.c.rej
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
Hunk #2 succeeded at 74 (offset -1 lines).
Hunk #3 succeeded at 247 (offset 14 lines).
Hunk #4 succeeded at 265 (offset 14 lines).
Hunk #5 succeeded at 317 (offset 14 lines).
patching file drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
Hunk #3 succeeded at 89 with fuzz 1 (offset -2 lines).
Hunk #4 succeeded at 95 (offset -11 lines).
Hunk #5 succeeded at 110 (offset -11 lines).
patching file mk/rte.app.mk


DPDK STV team

                 reply	other threads:[~2017-07-05 19:15 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$12qa5m1@fmsmga001.fm.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).