From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw21535 [PATCH v2 06/14] ring: remove watermark support
Date: 08 Mar 2017 12:43:15 -0800 [thread overview]
Message-ID: <63cbe6$11ut0d0@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 11336 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21535
_apply patch file failure_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue, 7 Mar 2017 11:32:09 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
Repo:dpdk-next-crypto, Branch:master, CommitID:13f57aba3e9f4f6818f525c2e402ac75d5ec7967
Repo:dpdk-next-net, Branch:master, CommitID:ce47e382ceaf2ab0515051cefbd9987c81da4ede
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:c9051455d6bcd4bfdffdc83c8f2c329a7534921c
Apply patch file failed:
Repo: dpdk
21535:
patching file doc/guides/prog_guide/ring_lib.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/prog_guide/ring_lib.rst.rej
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 118.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file examples/Makefile
patching file lib/librte_ring/rte_ring.c
Hunk #1 FAILED at 138.
Hunk #2 FAILED at 256.
Hunk #3 FAILED at 287.
3 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 #1 FAILED at 156.
Hunk #2 succeeded at 194 (offset 23 lines).
Hunk #3 succeeded at 320 (offset 44 lines).
Hunk #4 succeeded at 400 (offset 44 lines).
Hunk #5 FAILED at 370.
Hunk #6 FAILED at 411.
Hunk #7 succeeded at 567 with fuzz 1 (offset 141 lines).
Hunk #8 succeeded at 754 with fuzz 2 (offset 309 lines).
Hunk #9 FAILED at 457.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 660.
Hunk #12 succeeded at 800 (offset 118 lines).
Hunk #13 succeeded at 824 with fuzz 1 (offset 118 lines).
Hunk #14 succeeded at 841 (offset 111 lines).
Hunk #15 succeeded at 862 (offset 115 lines).
Hunk #16 FAILED at 768.
7 out of 16 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/autotest_test_funcs.py
patching file test/test/commands.c
patching file test/test/test_ring.c
Hunk #2 FAILED at 100.
Hunk #5 succeeded at 1324 (offset 410 lines).
1 out of 5 hunks FAILED -- saving rejects to file test/test/test_ring.c.rej
Repo: dpdk-next-crypto
21535:
patching file doc/guides/prog_guide/ring_lib.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/prog_guide/ring_lib.rst.rej
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 118.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file examples/Makefile
patching file lib/librte_ring/rte_ring.c
Hunk #1 FAILED at 138.
Hunk #2 FAILED at 256.
Hunk #3 FAILED at 287.
3 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 #1 FAILED at 156.
Hunk #2 succeeded at 194 (offset 23 lines).
Hunk #3 succeeded at 320 (offset 44 lines).
Hunk #4 succeeded at 400 (offset 44 lines).
Hunk #5 FAILED at 370.
Hunk #6 FAILED at 411.
Hunk #7 succeeded at 567 with fuzz 1 (offset 141 lines).
Hunk #8 succeeded at 754 with fuzz 2 (offset 309 lines).
Hunk #9 FAILED at 457.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 660.
Hunk #12 succeeded at 800 (offset 118 lines).
Hunk #13 succeeded at 824 with fuzz 1 (offset 118 lines).
Hunk #14 succeeded at 841 (offset 111 lines).
Hunk #15 succeeded at 862 (offset 115 lines).
Hunk #16 FAILED at 768.
7 out of 16 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/autotest_test_funcs.py
patching file test/test/commands.c
patching file test/test/test_ring.c
Hunk #2 FAILED at 100.
Hunk #5 succeeded at 1324 (offset 410 lines).
1 out of 5 hunks FAILED -- saving rejects to file test/test/test_ring.c.rej
Repo: dpdk-next-net
21535:
patching file doc/guides/prog_guide/ring_lib.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/prog_guide/ring_lib.rst.rej
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 118.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file examples/Makefile
patching file lib/librte_ring/rte_ring.c
Hunk #1 FAILED at 138.
Hunk #2 FAILED at 256.
Hunk #3 FAILED at 287.
3 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 #1 FAILED at 156.
Hunk #2 succeeded at 194 (offset 23 lines).
Hunk #3 succeeded at 320 (offset 44 lines).
Hunk #4 succeeded at 400 (offset 44 lines).
Hunk #5 FAILED at 370.
Hunk #6 FAILED at 411.
Hunk #7 succeeded at 567 with fuzz 1 (offset 141 lines).
Hunk #8 succeeded at 754 with fuzz 2 (offset 309 lines).
Hunk #9 FAILED at 457.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 660.
Hunk #12 succeeded at 800 (offset 118 lines).
Hunk #13 succeeded at 824 with fuzz 1 (offset 118 lines).
Hunk #14 succeeded at 841 (offset 111 lines).
Hunk #15 succeeded at 862 (offset 115 lines).
Hunk #16 FAILED at 768.
7 out of 16 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/autotest_test_funcs.py
patching file test/test/commands.c
patching file test/test/test_ring.c
Hunk #2 FAILED at 100.
Hunk #5 succeeded at 1324 (offset 410 lines).
1 out of 5 hunks FAILED -- saving rejects to file test/test/test_ring.c.rej
Repo: dpdk-next-virtio
21535:
patching file doc/guides/prog_guide/ring_lib.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/prog_guide/ring_lib.rst.rej
patching file doc/guides/rel_notes/release_17_05.rst
Hunk #1 FAILED at 118.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_17_05.rst.rej
patching file examples/Makefile
patching file lib/librte_ring/rte_ring.c
Hunk #1 FAILED at 138.
Hunk #2 FAILED at 256.
Hunk #3 FAILED at 287.
3 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 #1 FAILED at 156.
Hunk #2 succeeded at 194 (offset 23 lines).
Hunk #3 succeeded at 320 (offset 44 lines).
Hunk #4 succeeded at 400 (offset 44 lines).
Hunk #5 FAILED at 370.
Hunk #6 FAILED at 411.
Hunk #7 succeeded at 567 with fuzz 1 (offset 141 lines).
Hunk #8 succeeded at 754 with fuzz 2 (offset 309 lines).
Hunk #9 FAILED at 457.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 660.
Hunk #12 succeeded at 800 (offset 118 lines).
Hunk #13 succeeded at 824 with fuzz 1 (offset 118 lines).
Hunk #14 succeeded at 841 (offset 111 lines).
Hunk #15 succeeded at 862 (offset 115 lines).
Hunk #16 FAILED at 768.
7 out of 16 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
can't find file to patch at input line 273
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/autotest_test_funcs.py b/test/test/autotest_test_funcs.py
|index 1c5f390..8da8fcd 100644
|--- a/test/test/autotest_test_funcs.py
|+++ b/test/test/autotest_test_funcs.py
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 289
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/commands.c b/test/test/commands.c
|index 2df46b0..551c81d 100644
|--- a/test/test/commands.c
|+++ b/test/test/commands.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 359
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_ring.c b/test/test/test_ring.c
|index 3891f5d..666a451 100644
|--- a/test/test/test_ring.c
|+++ b/test/test/test_ring.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
5 out of 5 hunks ignored
Repo: dpdk-next-eventdev
21535:
patching file doc/guides/prog_guide/ring_lib.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/prog_guide/ring_lib.rst.rej
can't find file to patch at input line 24
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 c69ca8f..4e748dc 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 examples/Makefile
patching file lib/librte_ring/rte_ring.c
Hunk #1 FAILED at 138.
Hunk #2 FAILED at 256.
Hunk #3 FAILED at 287.
3 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 #1 FAILED at 156.
Hunk #2 succeeded at 194 (offset 23 lines).
Hunk #3 succeeded at 320 (offset 44 lines).
Hunk #4 succeeded at 400 (offset 44 lines).
Hunk #5 FAILED at 370.
Hunk #6 FAILED at 411.
Hunk #7 succeeded at 567 with fuzz 1 (offset 141 lines).
Hunk #8 succeeded at 754 with fuzz 2 (offset 309 lines).
Hunk #9 FAILED at 457.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 660.
Hunk #12 succeeded at 800 (offset 118 lines).
Hunk #13 succeeded at 824 with fuzz 1 (offset 118 lines).
Hunk #14 succeeded at 841 (offset 111 lines).
Hunk #15 succeeded at 862 (offset 115 lines).
Hunk #16 FAILED at 768.
7 out of 16 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
can't find file to patch at input line 273
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/autotest_test_funcs.py b/test/test/autotest_test_funcs.py
|index 1c5f390..8da8fcd 100644
|--- a/test/test/autotest_test_funcs.py
|+++ b/test/test/autotest_test_funcs.py
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 289
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/commands.c b/test/test/commands.c
|index 2df46b0..551c81d 100644
|--- a/test/test/commands.c
|+++ b/test/test/commands.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 359
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/test/test/test_ring.c b/test/test/test_ring.c
|index 3891f5d..666a451 100644
|--- a/test/test/test_ring.c
|+++ b/test/test/test_ring.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
5 out of 5 hunks ignored
DPDK STV team
reply other threads:[~2017-03-08 20:43 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='63cbe6$11ut0d0@fmsmga002.fm.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).