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| pw26222 [PATCH v3 04/12] cryptodev: do not create session mempool internally
Date: 04 Jul 2017 19:57:46 -0700	[thread overview]
Message-ID: <e81775$12q07s0@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Sun,  2 Jul 2017 16:57:15 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:9fc7090f258bb1a5b624f8ebbec551d0017c1399
                   Repo:dpdk-next-crypto, Branch:master, CommitID:d76af7bf88a91d9e3fec9cd1af8e59421fe70765
                   Repo:dpdk-next-net, Branch:master, CommitID:d8ee8d7efc25a5ac0c3fca765f2244955ce8adac
                   Repo:dpdk-next-virtio, Branch:master, CommitID:98b53e38c195c0140d1b9d5b412986f3b92cfcf3
                   Repo:dpdk, Branch:master, CommitID:ad10c178210e11bfa468f7f5ecca597644d2eb34
                   
Apply patch file failed:
Repo: dpdk
26222:
patching file app/test-crypto-perf/main.c
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/scheduler_pmd_ops.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.h
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 466 (offset 38 lines).
Hunk #2 succeeded at 477 (offset 38 lines).
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 67 (offset 1 line).
Hunk #2 succeeded at 416 (offset 33 lines).
Hunk #3 succeeded at 464 (offset 33 lines).
Hunk #4 succeeded at 489 (offset 33 lines).
Hunk #5 succeeded at 574 (offset 33 lines).
Hunk #6 succeeded at 610 (offset 33 lines).
Hunk #7 succeeded at 619 (offset 33 lines).
Hunk #8 succeeded at 640 (offset 33 lines).
Hunk #9 succeeded at 651 (offset 33 lines).
Hunk #10 succeeded at 680 (offset 33 lines).
Hunk #11 succeeded at 7868 with fuzz 1 (offset 5 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #2 succeeded at 403 (offset 8 lines).
Hunk #3 succeeded at 448 (offset 8 lines).

Repo: dpdk-next-crypto
26222:
patching file app/test-crypto-perf/main.c
Hunk #1 succeeded at 43 (offset 32 lines).
Hunk #2 succeeded at 79 (offset 32 lines).
Hunk #3 succeeded at 103 (offset 32 lines).
Hunk #4 succeeded at 382 (offset 65 lines).
Hunk #5 succeeded at 418 (offset 65 lines).
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/scheduler_pmd_ops.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.h
Hunk #1 succeeded at 143 (offset 4 lines).
Hunk #2 succeeded at 162 (offset 4 lines).
patching file examples/l2fwd-crypto/main.c
Hunk #1 succeeded at 88 with fuzz 2.
Hunk #2 succeeded at 251 (offset 26 lines).
Hunk #3 succeeded at 646 (offset 56 lines).
Hunk #4 succeeded at 664 (offset 58 lines).
Hunk #5 succeeded at 685 (offset 58 lines).
Hunk #6 succeeded at 788 with fuzz 1 (offset 88 lines).
Hunk #7 FAILED at 1554.
Hunk #8 succeeded at 1933 (offset 371 lines).
Hunk #9 succeeded at 2062 with fuzz 2 (offset 477 lines).
Hunk #10 succeeded at 2220 (offset 386 lines).
Hunk #11 succeeded at 2230 (offset 386 lines).
1 out of 11 hunks FAILED -- saving rejects to file examples/l2fwd-crypto/main.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 succeeded at 744 (offset 61 lines).
Hunk #2 succeeded at 766 (offset 61 lines).
Hunk #3 succeeded at 777 (offset 61 lines).
Hunk #4 succeeded at 1095 (offset 61 lines).
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 514 (offset 86 lines).
Hunk #2 succeeded at 525 (offset 86 lines).
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 67 (offset 1 line).
Hunk #2 succeeded at 386 (offset 3 lines).
Hunk #3 succeeded at 434 (offset 3 lines).
Hunk #4 succeeded at 459 (offset 3 lines).
Hunk #5 succeeded at 544 (offset 3 lines).
Hunk #6 succeeded at 580 (offset 3 lines).
Hunk #7 succeeded at 589 (offset 3 lines).
Hunk #8 succeeded at 610 (offset 3 lines).
Hunk #9 succeeded at 621 (offset 3 lines).
Hunk #10 succeeded at 650 (offset 3 lines).
Hunk #11 succeeded at 7709 (offset -154 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #1 succeeded at 53 (offset 3 lines).
Hunk #2 succeeded at 405 (offset 10 lines).
Hunk #3 succeeded at 450 (offset 10 lines).

Repo: dpdk-next-net
26222:
patching file app/test-crypto-perf/main.c
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/scheduler_pmd_ops.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.h
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 466 (offset 38 lines).
Hunk #2 succeeded at 477 (offset 38 lines).
patching file test/test/test_cryptodev.c
Hunk #2 succeeded at 415 (offset 32 lines).
Hunk #3 succeeded at 463 (offset 32 lines).
Hunk #4 succeeded at 488 (offset 32 lines).
Hunk #5 succeeded at 573 (offset 32 lines).
Hunk #6 succeeded at 609 (offset 32 lines).
Hunk #7 succeeded at 618 (offset 32 lines).
Hunk #8 succeeded at 639 (offset 32 lines).
Hunk #9 succeeded at 650 (offset 32 lines).
Hunk #10 succeeded at 679 (offset 32 lines).
Hunk #11 succeeded at 7867 with fuzz 1 (offset 4 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #2 succeeded at 403 (offset 8 lines).
Hunk #3 succeeded at 448 (offset 8 lines).

Repo: dpdk-next-virtio
26222:
patching file app/test-crypto-perf/main.c
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/scheduler_pmd_ops.c
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.h
patching file examples/l2fwd-crypto/main.c
patching file lib/librte_cryptodev/rte_cryptodev.c
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 466 (offset 38 lines).
Hunk #2 succeeded at 477 (offset 38 lines).
patching file test/test/test_cryptodev.c
Hunk #2 succeeded at 415 (offset 32 lines).
Hunk #3 succeeded at 463 (offset 32 lines).
Hunk #4 succeeded at 488 (offset 32 lines).
Hunk #5 succeeded at 573 (offset 32 lines).
Hunk #6 succeeded at 609 (offset 32 lines).
Hunk #7 succeeded at 618 (offset 32 lines).
Hunk #8 succeeded at 639 (offset 32 lines).
Hunk #9 succeeded at 650 (offset 32 lines).
Hunk #10 succeeded at 679 (offset 32 lines).
Hunk #11 succeeded at 7867 with fuzz 1 (offset 4 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #2 succeeded at 403 (offset 8 lines).
Hunk #3 succeeded at 448 (offset 8 lines).

Repo: dpdk-next-eventdev
26222:
patching file app/test-crypto-perf/main.c
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/scheduler_pmd_ops.c
Hunk #1 succeeded at 84 (offset -1 lines).
Hunk #2 succeeded at 95 (offset -1 lines).
patching file examples/ipsec-secgw/ipsec-secgw.c
patching file examples/ipsec-secgw/ipsec.h
patching file examples/l2fwd-crypto/main.c
Hunk #7 succeeded at 1553 (offset -1 lines).
Hunk #8 succeeded at 1562 (offset -1 lines).
Hunk #9 succeeded at 1585 (offset -1 lines).
Hunk #10 succeeded at 1834 (offset -1 lines).
Hunk #11 succeeded at 1844 (offset -1 lines).
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 succeeded at 934 (offset 251 lines).
Hunk #2 succeeded at 956 (offset 251 lines).
Hunk #3 succeeded at 967 (offset 251 lines).
Hunk #4 succeeded at 1287 (offset 253 lines).
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 493 (offset 65 lines).
Hunk #2 succeeded at 504 (offset 65 lines).
patching file test/test/test_cryptodev.c
Hunk #2 succeeded at 415 (offset 32 lines).
Hunk #3 succeeded at 463 (offset 32 lines).
Hunk #4 succeeded at 488 (offset 32 lines).
Hunk #5 succeeded at 573 (offset 32 lines).
Hunk #6 succeeded at 609 (offset 32 lines).
Hunk #7 succeeded at 618 (offset 32 lines).
Hunk #8 succeeded at 639 (offset 32 lines).
Hunk #9 succeeded at 650 (offset 32 lines).
Hunk #10 succeeded at 679 (offset 32 lines).
Hunk #11 succeeded at 7869 with fuzz 1 (offset 6 lines).
patching file test/test/test_cryptodev_perf.c
Hunk #2 succeeded at 454 (offset 59 lines).
Hunk #3 succeeded at 499 (offset 59 lines).


DPDK STV team

             reply	other threads:[~2017-07-05  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05  2:57 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-07-03  0:57 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='e81775$12q07s0@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).