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| pw22640 [PATCH v4 02/14] ring: create common structure for prod and cons metadata
Date: 29 Mar 2017 05:58:52 -0700	[thread overview]
Message-ID: <e81775$11k64e0@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue, 28 Mar 2017 21:35:54 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
                   Repo:dpdk-next-crypto, Branch:master, CommitID:3eacd5a3ef2aa2f811b943659560c37fbd332b84
                   Repo:dpdk-next-net, Branch:master, CommitID:d1f78e9696cd39a5faed498ad7e8368c724945e4
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8ec4aa31199c361151610ef54427d5f91c3dac8c
                   Repo:dpdk, Branch:master, CommitID:b88161be422750fca0e66c76385d3d00912ba8fb
                   
Apply patch file failed:
Repo: dpdk
22640:
patching file lib/librte_pdump/rte_pdump.c
patching file lib/librte_port/rte_port_ring.c
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 147 (offset 2 lines).
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 139 with fuzz 2 (offset -8 lines).
Hunk #3 FAILED at 179.
Hunk #4 succeeded at 843 (offset -4 lines).
Hunk #5 succeeded at 910 (offset -4 lines).
Hunk #6 succeeded at 981 (offset -4 lines).
Hunk #7 succeeded at 1045 (offset -4 lines).
Hunk #8 succeeded at 1212 (offset -4 lines).
Hunk #9 succeeded at 1280 (offset -4 lines).
1 out of 9 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej

Repo: dpdk-next-crypto
22640:
patching file lib/librte_pdump/rte_pdump.c
patching file lib/librte_port/rte_port_ring.c
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 147 (offset 2 lines).
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 139 with fuzz 2 (offset -8 lines).
Hunk #3 FAILED at 179.
Hunk #4 succeeded at 843 (offset -4 lines).
Hunk #5 succeeded at 910 (offset -4 lines).
Hunk #6 succeeded at 981 (offset -4 lines).
Hunk #7 succeeded at 1045 (offset -4 lines).
Hunk #8 succeeded at 1212 (offset -4 lines).
Hunk #9 succeeded at 1280 (offset -4 lines).
1 out of 9 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej

Repo: dpdk-next-net
22640:
patching file lib/librte_pdump/rte_pdump.c
patching file lib/librte_port/rte_port_ring.c
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 147 (offset 2 lines).
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 139 with fuzz 2 (offset -8 lines).
Hunk #3 FAILED at 179.
Hunk #4 succeeded at 843 (offset -4 lines).
Hunk #5 succeeded at 910 (offset -4 lines).
Hunk #6 succeeded at 981 (offset -4 lines).
Hunk #7 succeeded at 1045 (offset -4 lines).
Hunk #8 succeeded at 1212 (offset -4 lines).
Hunk #9 succeeded at 1280 (offset -4 lines).
1 out of 9 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej

Repo: dpdk-next-virtio
22640:
patching file lib/librte_pdump/rte_pdump.c
patching file lib/librte_port/rte_port_ring.c
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 147 (offset 2 lines).
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 139 with fuzz 2 (offset -8 lines).
Hunk #3 FAILED at 179.
Hunk #4 succeeded at 843 (offset -4 lines).
Hunk #5 succeeded at 910 (offset -4 lines).
Hunk #6 succeeded at 981 (offset -4 lines).
Hunk #7 succeeded at 1045 (offset -4 lines).
Hunk #8 succeeded at 1212 (offset -4 lines).
Hunk #9 succeeded at 1280 (offset -4 lines).
1 out of 9 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej

Repo: dpdk-next-eventdev
22640:
patching file lib/librte_pdump/rte_pdump.c
patching file lib/librte_port/rte_port_ring.c
patching file lib/librte_ring/rte_ring.c
Hunk #1 succeeded at 147 (offset 2 lines).
patching file lib/librte_ring/rte_ring.h
Hunk #2 succeeded at 139 with fuzz 2 (offset -8 lines).
Hunk #3 FAILED at 179.
Hunk #4 succeeded at 843 (offset -4 lines).
Hunk #5 succeeded at 910 (offset -4 lines).
Hunk #6 succeeded at 981 (offset -4 lines).
Hunk #7 succeeded at 1045 (offset -4 lines).
Hunk #8 succeeded at 1212 (offset -4 lines).
Hunk #9 succeeded at 1280 (offset -4 lines).
1 out of 9 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej


DPDK STV team

                 reply	other threads:[~2017-03-29 13:00 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$11k64e0@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).