* [dpdk-test-report] |FAILURE| pw26510 [PATCH v3] crypto/scheduler: add multicore scheduling mode
@ 2017-07-07 5:36 sys_stv
0 siblings, 0 replies; only message in thread
From: sys_stv @ 2017-07-07 5:36 UTC (permalink / raw)
To: test-report; +Cc: kirill.rybalchenko
[-- Attachment #1: Type: text/plain, Size: 6977 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26510
_apply patch file failure_
Submitter: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Date: Wed, 5 Jul 2017 17:14:38 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:2d3702e50c9428a108146bf7f7db306dc163700f
Repo:dpdk-next-crypto, Branch:master, CommitID:324377c6f82a9274a489f3a31e1d1feef9a29aed
Repo:dpdk-next-net, Branch:master, CommitID:fe6ffaf83cf9e2130ddda2fc6f6b5cbc9176f27b
Repo:dpdk-next-virtio, Branch:master, CommitID:96b1a3ad514de2a5d3fc8a12e11b9002764c1e9f
Repo:dpdk, Branch:master, CommitID:cfea1f3048d1bfda61036e6f823949fba4d692d4
Apply patch file failed:
Repo: dpdk
26510:
patching file doc/guides/cryptodevs/scheduler.rst
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 99 with fuzz 2 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/Makefile
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
patching file drivers/crypto/scheduler/scheduler_multicore.c
patching file drivers/crypto/scheduler/scheduler_pmd.c
Hunk #1 succeeded at 47 (offset -2 lines).
Hunk #2 succeeded at 59 (offset -2 lines).
Hunk #3 succeeded at 69 (offset -2 lines).
Hunk #4 succeeded at 85 (offset -2 lines).
Hunk #5 succeeded at 127 (offset -2 lines).
Hunk #6 succeeded at 260 (offset -2 lines).
Hunk #7 succeeded at 416 (offset -2 lines).
Hunk #8 succeeded at 489 (offset -2 lines).
patching file drivers/crypto/scheduler/scheduler_pmd_private.h
Hunk #1 succeeded at 86 (offset -3 lines).
Hunk #2 succeeded at 141 (offset -5 lines).
Repo: dpdk-next-crypto
26510:
patching file doc/guides/cryptodevs/scheduler.rst
Hunk #1 FAILED at 170.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/cryptodevs/scheduler.rst.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.
2 out of 2 hunks ignored -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/crypto/scheduler/Makefile.rej
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 358 (offset 7 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
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/scheduler/rte_cryptodev_scheduler.h.rej
The next patch would create the file drivers/crypto/scheduler/scheduler_multicore.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/crypto/scheduler/scheduler_pmd.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
8 out of 8 hunks ignored -- saving rejects to file drivers/crypto/scheduler/scheduler_pmd.c.rej
patching file drivers/crypto/scheduler/scheduler_pmd_private.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/scheduler/scheduler_pmd_private.h.rej
Repo: dpdk-next-net
26510:
patching file doc/guides/cryptodevs/scheduler.rst
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 105 with fuzz 2 (offset 5 lines).
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/Makefile
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
patching file drivers/crypto/scheduler/scheduler_multicore.c
patching file drivers/crypto/scheduler/scheduler_pmd.c
Hunk #1 succeeded at 47 (offset -2 lines).
Hunk #2 succeeded at 59 (offset -2 lines).
Hunk #3 succeeded at 69 (offset -2 lines).
Hunk #4 succeeded at 85 (offset -2 lines).
Hunk #5 succeeded at 127 (offset -2 lines).
Hunk #6 succeeded at 260 (offset -2 lines).
Hunk #7 succeeded at 416 (offset -2 lines).
Hunk #8 succeeded at 489 (offset -2 lines).
patching file drivers/crypto/scheduler/scheduler_pmd_private.h
Hunk #1 succeeded at 86 (offset -3 lines).
Hunk #2 succeeded at 141 (offset -5 lines).
Repo: dpdk-next-virtio
26510:
patching file doc/guides/cryptodevs/scheduler.rst
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 99 with fuzz 2 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/Makefile
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
patching file drivers/crypto/scheduler/scheduler_multicore.c
patching file drivers/crypto/scheduler/scheduler_pmd.c
Hunk #1 succeeded at 47 (offset -2 lines).
Hunk #2 succeeded at 59 (offset -2 lines).
Hunk #3 succeeded at 69 (offset -2 lines).
Hunk #4 succeeded at 85 (offset -2 lines).
Hunk #5 succeeded at 127 (offset -2 lines).
Hunk #6 succeeded at 260 (offset -2 lines).
Hunk #7 succeeded at 416 (offset -2 lines).
Hunk #8 succeeded at 489 (offset -2 lines).
patching file drivers/crypto/scheduler/scheduler_pmd_private.h
Hunk #1 succeeded at 86 (offset -3 lines).
Hunk #2 succeeded at 141 (offset -5 lines).
Repo: dpdk-next-eventdev
26510:
patching file doc/guides/cryptodevs/scheduler.rst
patching file doc/guides/rel_notes/release_17_08.rst
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 99 with fuzz 2 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_08.rst.rej
patching file drivers/crypto/scheduler/Makefile
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #3 succeeded at 334 (offset 32 lines).
patching file drivers/crypto/scheduler/scheduler_multicore.c
patching file drivers/crypto/scheduler/scheduler_pmd.c
Hunk #1 succeeded at 46 (offset -3 lines).
Hunk #2 succeeded at 58 (offset -3 lines).
Hunk #3 succeeded at 68 (offset -3 lines).
Hunk #4 succeeded at 84 (offset -3 lines).
Hunk #5 succeeded at 124 (offset -5 lines).
Hunk #6 succeeded at 273 (offset 11 lines).
Hunk #7 succeeded at 429 (offset 11 lines).
Hunk #8 succeeded at 508 with fuzz 1 (offset 17 lines).
patching file drivers/crypto/scheduler/scheduler_pmd_private.h
Hunk #1 succeeded at 86 (offset -3 lines).
Hunk #2 succeeded at 141 (offset -5 lines).
DPDK STV team
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-07-07 5:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-07 5:36 [dpdk-test-report] |FAILURE| pw26510 [PATCH v3] crypto/scheduler: add multicore scheduling mode sys_stv
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).