automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: wei.zhao1@intel.com
Subject: [dpdk-test-report] |FAILURE| pw19174 [PATCH v3 4/9] net/ixgbe: restore n-tuple filter Add support for restoring n-tuple filter in SW.
Date: 12 Jan 2017 06:42:43 -0800	[thread overview]
Message-ID: <e624e2$1081uvo@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: zhao wei <wei.zhao1@intel.com>
Date: Thu, 12 Jan 2017 16:13:45 +0800
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:afe425f602a8bea436b83d664025a95d69b722ae
                   Repo:dpdk-next-net, Branch:master, CommitID:aaa9bebd57d51c5529201445ab1ac26a6656ce46
                   Repo:dpdk-next-virtio, Branch:master, CommitID:2b2669fc4c792f9a3ab73490bb93f7810a71c089
                   Repo:dpdk, Branch:master, CommitID:6de5c0f1302cc9e310a47e3488d7d3f1a4602b64
                   
Apply patch file failed:
Repo: dpdk-next-virtio
19174:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #2 succeeded at 386 (offset -2 lines).
Hunk #3 succeeded at 1350 with fuzz 2 (offset 13 lines).
Hunk #4 succeeded at 2543 (offset 17 lines).
Hunk #5 FAILED at 2547.
Hunk #6 succeeded at 2604 (offset 17 lines).
Hunk #7 succeeded at 5762 (offset -86 lines).
Hunk #8 succeeded at 5825 (offset -86 lines).
Hunk #9 succeeded at 5850 (offset -86 lines).
Hunk #10 succeeded at 7958 with fuzz 1 (offset 8 lines).
1 out of 10 hunks FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej


DPDK STV team

                 reply	other threads:[~2017-01-12 14:42 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='e624e2$1081uvo@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=wei.zhao1@intel.com \
    /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).