automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: beilei.xing@intel.com
Subject: [dpdk-test-report] |FAILURE| pw22871 [PATCH v5 4/4] net/i40e: enable tunnel filter for MPLS
Date: 30 Mar 2017 18:14:57 -0700	[thread overview]
Message-ID: <e81775$11kqjgb@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Beilei Xing <beilei.xing@intel.com>
Date: Thu, 30 Mar 2017 14:56:35 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
                   Repo:dpdk-next-crypto, Branch:master, CommitID:185d7ec1ca04d5bcab193adc2d61fc47cf6ca7d5
                   Repo:dpdk-next-net, Branch:master, CommitID:70b78743d731f3b7b571bce9e996ab2b08cd8e13
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8ec4aa31199c361151610ef54427d5f91c3dac8c
                   Repo:dpdk, Branch:master, CommitID:ba82829fda022e14a938c3a669de0e634626e4c8
                   
Apply patch file failed:
Repo: dpdk
22871:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 succeeded at 6781 with fuzz 2 (offset -154 lines).
Hunk #2 succeeded at 6908 with fuzz 1 (offset -155 lines).
Hunk #3 succeeded at 6952 with fuzz 1 (offset -160 lines).
Hunk #4 FAILED at 7151.
Hunk #5 FAILED at 7191.
Hunk #6 FAILED at 7201.
Hunk #7 FAILED at 10587.
Hunk #8 FAILED at 10602.
5 out of 8 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 succeeded at 499 (offset -2 lines).
Hunk #2 succeeded at 626 (offset -47 lines).
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 succeeded at 1920 with fuzz 1 (offset -16 lines).
Hunk #2 FAILED at 1952.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej

Repo: dpdk-next-crypto
22871:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 succeeded at 6779 with fuzz 2 (offset -156 lines).
Hunk #2 succeeded at 6906 with fuzz 1 (offset -157 lines).
Hunk #3 succeeded at 6950 with fuzz 1 (offset -162 lines).
Hunk #4 FAILED at 7151.
Hunk #5 FAILED at 7191.
Hunk #6 FAILED at 7201.
Hunk #7 FAILED at 10587.
Hunk #8 FAILED at 10602.
5 out of 8 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 succeeded at 499 (offset -2 lines).
Hunk #2 succeeded at 626 (offset -47 lines).
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 succeeded at 1920 with fuzz 1 (offset -16 lines).
Hunk #2 FAILED at 1952.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej

Repo: dpdk-next-net
22871:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 succeeded at 7044 with fuzz 1 (offset 109 lines).
Hunk #2 FAILED at 7063.
Hunk #3 succeeded at 7253 with fuzz 2 (offset 143 lines).
Hunk #4 FAILED at 7149.
Hunk #5 FAILED at 7189.
Hunk #6 FAILED at 7199.
Hunk #7 FAILED at 10585.
Hunk #8 FAILED at 10600.
6 out of 8 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
patching file drivers/net/i40e/i40e_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej

Repo: dpdk-next-virtio
22871:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 succeeded at 6779 with fuzz 2 (offset -156 lines).
Hunk #2 succeeded at 6906 with fuzz 1 (offset -157 lines).
Hunk #3 succeeded at 6950 with fuzz 1 (offset -162 lines).
Hunk #4 FAILED at 7151.
Hunk #5 FAILED at 7191.
Hunk #6 FAILED at 7201.
Hunk #7 FAILED at 10587.
Hunk #8 FAILED at 10602.
5 out of 8 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 succeeded at 499 (offset -2 lines).
Hunk #2 succeeded at 626 (offset -47 lines).
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 succeeded at 1920 with fuzz 1 (offset -16 lines).
Hunk #2 FAILED at 1952.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej

Repo: dpdk-next-eventdev
22871:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #1 succeeded at 6779 with fuzz 2 (offset -156 lines).
Hunk #2 succeeded at 6906 with fuzz 1 (offset -157 lines).
Hunk #3 succeeded at 6950 with fuzz 1 (offset -162 lines).
Hunk #4 FAILED at 7151.
Hunk #5 FAILED at 7191.
Hunk #6 FAILED at 7201.
Hunk #7 FAILED at 10587.
Hunk #8 FAILED at 10602.
5 out of 8 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 succeeded at 499 (offset -2 lines).
Hunk #2 succeeded at 626 (offset -47 lines).
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 succeeded at 1920 with fuzz 1 (offset -16 lines).
Hunk #2 FAILED at 1952.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej


DPDK STV team

                 reply	other threads:[~2017-03-31  1:14 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$11kqjgb@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=beilei.xing@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).