From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw20703 [PATCH v1 04/14] ring: remove debug setting
Date: 23 Feb 2017 11:27:14 -0800 [thread overview]
Message-ID: <ffb989$1hhnc9@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7043 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/20703
_apply patch file failure_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Thu, 23 Feb 2017 17:23:57 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:84e6e60a58c840a2fd3c5d6a6f23941b2648cf1c
Repo:dpdk-next-crypto, Branch:master, CommitID:3ef24b3d35d732c18ea3d68b30979506bfb1320e
Repo:dpdk-next-net, Branch:master, CommitID:608ce0d3d29f6089a2d97c80934fc7a7641be07c
Repo:dpdk-next-virtio, Branch:master, CommitID:850110f0e9c25f6b8a22447e4795a89847c1d00e
Repo:dpdk, Branch:master, CommitID:3ef24b3d35d732c18ea3d68b30979506bfb1320e
Apply patch file failed:
Repo: dpdk
20703:
patching file app/test/test_ring.c
patching file config/common_base
Hunk #1 FAILED at 447.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file doc/guides/prog_guide/ring_lib.rst
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 133 with fuzz 1 (offset 2 lines).
Hunk #2 succeeded at 280 with fuzz 1 (offset 2 lines).
Hunk #3 FAILED at 291.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.c.rej
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 165 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 176 (offset 4 lines).
Hunk #4 succeeded at 416 (offset 4 lines).
Hunk #5 FAILED at 432.
Hunk #6 succeeded at 508 (offset 4 lines).
Hunk #7 FAILED at 522.
Hunk #8 succeeded at 598 (offset 4 lines).
Hunk #9 succeeded at 632 (offset 4 lines).
Hunk #10 succeeded at 678 (offset 4 lines).
Hunk #11 succeeded at 694 (offset 4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-crypto
20703:
patching file app/test/test_ring.c
patching file config/common_base
Hunk #1 FAILED at 447.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file doc/guides/prog_guide/ring_lib.rst
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 133 with fuzz 1 (offset 2 lines).
Hunk #2 succeeded at 280 with fuzz 1 (offset 2 lines).
Hunk #3 FAILED at 291.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.c.rej
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 165 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 176 (offset 4 lines).
Hunk #4 succeeded at 416 (offset 4 lines).
Hunk #5 FAILED at 432.
Hunk #6 succeeded at 508 (offset 4 lines).
Hunk #7 FAILED at 522.
Hunk #8 succeeded at 598 (offset 4 lines).
Hunk #9 succeeded at 632 (offset 4 lines).
Hunk #10 succeeded at 678 (offset 4 lines).
Hunk #11 succeeded at 694 (offset 4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-net
20703:
patching file app/test/test_ring.c
patching file config/common_base
Hunk #1 FAILED at 447.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file doc/guides/prog_guide/ring_lib.rst
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 133 with fuzz 1 (offset 2 lines).
Hunk #2 succeeded at 280 with fuzz 1 (offset 2 lines).
Hunk #3 FAILED at 291.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.c.rej
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 165 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 176 (offset 4 lines).
Hunk #4 succeeded at 416 (offset 4 lines).
Hunk #5 FAILED at 432.
Hunk #6 succeeded at 508 (offset 4 lines).
Hunk #7 FAILED at 522.
Hunk #8 succeeded at 598 (offset 4 lines).
Hunk #9 succeeded at 632 (offset 4 lines).
Hunk #10 succeeded at 678 (offset 4 lines).
Hunk #11 succeeded at 694 (offset 4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-virtio
20703:
patching file app/test/test_ring.c
patching file config/common_base
Hunk #1 FAILED at 447.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file doc/guides/prog_guide/ring_lib.rst
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 133 with fuzz 1 (offset 2 lines).
Hunk #2 succeeded at 280 with fuzz 1 (offset 2 lines).
Hunk #3 FAILED at 291.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.c.rej
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 165 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 176 (offset 4 lines).
Hunk #4 succeeded at 416 (offset 4 lines).
Hunk #5 FAILED at 432.
Hunk #6 succeeded at 508 (offset 4 lines).
Hunk #7 FAILED at 522.
Hunk #8 succeeded at 598 (offset 4 lines).
Hunk #9 succeeded at 632 (offset 4 lines).
Hunk #10 succeeded at 678 (offset 4 lines).
Hunk #11 succeeded at 694 (offset 4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-eventdev
20703:
patching file app/test/test_ring.c
patching file config/common_base
Hunk #1 FAILED at 447.
1 out of 1 hunk FAILED -- saving rejects to file config/common_base.rej
patching file doc/guides/prog_guide/ring_lib.rst
can't find file to patch at input line 463
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/rel_notes/release_17_05.rst b/doc/guides/rel_notes/release_17_05.rst
|index ea45e0c..e0ebd71 100644
|--- a/doc/guides/rel_notes/release_17_05.rst
|+++ b/doc/guides/rel_notes/release_17_05.rst
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 133 with fuzz 1 (offset 2 lines).
Hunk #2 succeeded at 280 with fuzz 1 (offset 2 lines).
Hunk #3 FAILED at 291.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.c.rej
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 165 with fuzz 2 (offset 4 lines).
Hunk #3 succeeded at 176 (offset 4 lines).
Hunk #4 succeeded at 416 (offset 4 lines).
Hunk #5 FAILED at 432.
Hunk #6 succeeded at 508 (offset 4 lines).
Hunk #7 FAILED at 522.
Hunk #8 succeeded at 598 (offset 4 lines).
Hunk #9 succeeded at 632 (offset 4 lines).
Hunk #10 succeeded at 678 (offset 4 lines).
Hunk #11 succeeded at 694 (offset 4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
DPDK STV team
reply other threads:[~2017-02-23 19:27 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='ffb989$1hhnc9@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=bruce.richardson@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).