automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw22346 [PATCH v3 04/14] ring: remove debug setting
Date: 26 Mar 2017 23:06:04 -0700	[thread overview]
Message-ID: <e81775$11j72uk@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Fri, 24 Mar 2017 17:09:58 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
                   Repo:dpdk-next-crypto, Branch:master, CommitID:1b16ada4eeeb8c021c6b91692d0b80ecb3d9702e
                   Repo:dpdk-next-net, Branch:master, CommitID:5cb145cbca4970246064762d7c5018792411e737
                   Repo:dpdk-next-virtio, Branch:master, CommitID:922c87ff9fc456921ee5b673ac747da420f63bae
                   Repo:dpdk, Branch:master, CommitID:84aac97b49994be6b461b46be160b47938e697b3
                   
Apply patch file failed:
Repo: dpdk
22346:
patching file config/common_base
Hunk #1 FAILED at 452.
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 126.
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 -1 lines).
Hunk #3 succeeded at 176 (offset -1 lines).
Hunk #4 succeeded at 416 (offset -1 lines).
Hunk #5 FAILED at 437.
Hunk #6 succeeded at 508 (offset -1 lines).
Hunk #7 FAILED at 527.
Hunk #8 succeeded at 598 (offset -1 lines).
Hunk #9 succeeded at 632 (offset -1 lines).
Hunk #10 succeeded at 678 (offset -1 lines).
Hunk #11 succeeded at 694 (offset -1 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/test_ring.c

Repo: dpdk-next-crypto
22346:
patching file config/common_base
Hunk #1 FAILED at 452.
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 126.
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 -1 lines).
Hunk #3 succeeded at 176 (offset -1 lines).
Hunk #4 succeeded at 416 (offset -1 lines).
Hunk #5 FAILED at 437.
Hunk #6 succeeded at 508 (offset -1 lines).
Hunk #7 FAILED at 527.
Hunk #8 succeeded at 598 (offset -1 lines).
Hunk #9 succeeded at 632 (offset -1 lines).
Hunk #10 succeeded at 678 (offset -1 lines).
Hunk #11 succeeded at 694 (offset -1 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/test_ring.c

Repo: dpdk-next-net
22346:
patching file config/common_base
Hunk #1 FAILED at 452.
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 126.
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 -1 lines).
Hunk #3 succeeded at 176 (offset -1 lines).
Hunk #4 succeeded at 416 (offset -1 lines).
Hunk #5 FAILED at 437.
Hunk #6 succeeded at 508 (offset -1 lines).
Hunk #7 FAILED at 527.
Hunk #8 succeeded at 598 (offset -1 lines).
Hunk #9 succeeded at 632 (offset -1 lines).
Hunk #10 succeeded at 678 (offset -1 lines).
Hunk #11 succeeded at 694 (offset -1 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/test_ring.c

Repo: dpdk-next-virtio
22346:
patching file config/common_base
Hunk #1 FAILED at 452.
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 126.
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 -1 lines).
Hunk #3 succeeded at 176 (offset -1 lines).
Hunk #4 succeeded at 416 (offset -1 lines).
Hunk #5 FAILED at 437.
Hunk #6 succeeded at 508 (offset -1 lines).
Hunk #7 FAILED at 527.
Hunk #8 succeeded at 598 (offset -1 lines).
Hunk #9 succeeded at 632 (offset -1 lines).
Hunk #10 succeeded at 678 (offset -1 lines).
Hunk #11 succeeded at 694 (offset -1 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/test_ring.c

Repo: dpdk-next-eventdev
22346:
patching file config/common_base
Hunk #1 FAILED at 452.
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 126.
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 -1 lines).
Hunk #3 succeeded at 176 (offset -1 lines).
Hunk #4 succeeded at 416 (offset -1 lines).
Hunk #5 FAILED at 437.
Hunk #6 succeeded at 508 (offset -1 lines).
Hunk #7 FAILED at 527.
Hunk #8 succeeded at 598 (offset -1 lines).
Hunk #9 succeeded at 632 (offset -1 lines).
Hunk #10 succeeded at 678 (offset -1 lines).
Hunk #11 succeeded at 694 (offset -1 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file test/test/test_ring.c


DPDK STV team

                 reply	other threads:[~2017-03-27  6:06 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$11j72uk@fmsmga001.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).