automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw21808 [PATCH] net/tap: support segmented mbufs
Date: 15 Mar 2017 17:02:52 -0700	[thread overview]
Message-ID: <e81775$11f25o2@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Wed, 15 Mar 2017 16:09:31 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:acd3b86bf98694fc5d418092edb740145d8214e1
                   Repo:dpdk-next-crypto, Branch:master, CommitID:6254e326fb9b1bce6dcbb1391c8d9a0cb5e864c2
                   Repo:dpdk-next-net, Branch:master, CommitID:1ab145a44f7822d05d4edb9398ae3c19c9c46b55
                   Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
                   Repo:dpdk, Branch:master, CommitID:d89a5bce1d20068035da613c455d1612c20eec5e
                   
Apply patch file failed:
Repo: dpdk
21808:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 32.
Hunk #2 FAILED at 49.
Hunk #3 FAILED at 125.
Hunk #4 succeeded at 200 (offset -88 lines).
Hunk #5 FAILED at 299.
Hunk #6 succeeded at 227 (offset -96 lines).
Hunk #7 FAILED at 335.
Hunk #8 succeeded at 378 (offset -140 lines).
Hunk #9 succeeded at 389 (offset -140 lines).
Hunk #10 succeeded at 402 (offset -140 lines).
Hunk #11 succeeded at 418 (offset -140 lines).
Hunk #12 succeeded at 451 (offset -142 lines).
Hunk #13 FAILED at 723.
Hunk #14 succeeded at 566 (offset -184 lines).
Hunk #15 FAILED at 772.
Hunk #16 succeeded at 599 (offset -185 lines).
7 out of 16 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 330
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index 9546411bd790..3ba57429d9c4 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-crypto
21808:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 32.
Hunk #2 FAILED at 49.
Hunk #3 FAILED at 125.
Hunk #4 succeeded at 200 (offset -88 lines).
Hunk #5 FAILED at 299.
Hunk #6 succeeded at 227 (offset -96 lines).
Hunk #7 FAILED at 335.
Hunk #8 succeeded at 378 (offset -140 lines).
Hunk #9 succeeded at 389 (offset -140 lines).
Hunk #10 succeeded at 402 (offset -140 lines).
Hunk #11 succeeded at 418 (offset -140 lines).
Hunk #12 succeeded at 451 (offset -142 lines).
Hunk #13 FAILED at 723.
Hunk #14 succeeded at 566 (offset -184 lines).
Hunk #15 FAILED at 772.
Hunk #16 succeeded at 599 (offset -185 lines).
7 out of 16 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 330
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index 9546411bd790..3ba57429d9c4 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-net
21808:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #2 succeeded at 49 with fuzz 1 (offset -1 lines).
Hunk #3 succeeded at 150 (offset 23 lines).
Hunk #4 succeeded at 262 (offset -32 lines).
Hunk #5 succeeded at 273 (offset -32 lines).
Hunk #6 succeeded at 341 (offset -32 lines).
Hunk #7 FAILED at 385.
Hunk #8 succeeded at 514 (offset -54 lines).
Hunk #9 succeeded at 525 (offset -54 lines).
Hunk #10 succeeded at 538 (offset -54 lines).
Hunk #11 succeeded at 554 (offset -54 lines).
Hunk #12 succeeded at 587 (offset -56 lines).
Hunk #13 FAILED at 773.
Hunk #14 succeeded at 735 (offset -65 lines).
Hunk #15 succeeded at 757 (offset -65 lines).
Hunk #16 succeeded at 779 (offset -65 lines).
2 out of 16 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 330
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index 9546411bd790..3ba57429d9c4 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-virtio
21808:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 32.
Hunk #2 FAILED at 49.
Hunk #3 FAILED at 125.
Hunk #4 succeeded at 200 (offset -88 lines).
Hunk #5 FAILED at 299.
Hunk #6 succeeded at 227 (offset -96 lines).
Hunk #7 FAILED at 335.
Hunk #8 succeeded at 378 (offset -140 lines).
Hunk #9 succeeded at 389 (offset -140 lines).
Hunk #10 succeeded at 402 (offset -140 lines).
Hunk #11 succeeded at 418 (offset -140 lines).
Hunk #12 succeeded at 451 (offset -142 lines).
Hunk #13 FAILED at 723.
Hunk #14 succeeded at 566 (offset -184 lines).
Hunk #15 FAILED at 772.
Hunk #16 succeeded at 599 (offset -185 lines).
7 out of 16 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 330
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index 9546411bd790..3ba57429d9c4 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored

Repo: dpdk-next-eventdev
21808:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 32.
Hunk #2 FAILED at 49.
Hunk #3 FAILED at 125.
Hunk #4 succeeded at 200 (offset -88 lines).
Hunk #5 FAILED at 299.
Hunk #6 succeeded at 227 (offset -96 lines).
Hunk #7 FAILED at 335.
Hunk #8 succeeded at 378 (offset -140 lines).
Hunk #9 succeeded at 389 (offset -140 lines).
Hunk #10 succeeded at 402 (offset -140 lines).
Hunk #11 succeeded at 418 (offset -140 lines).
Hunk #12 succeeded at 451 (offset -142 lines).
Hunk #13 FAILED at 723.
Hunk #14 succeeded at 566 (offset -184 lines).
Hunk #15 FAILED at 772.
Hunk #16 succeeded at 599 (offset -185 lines).
7 out of 16 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 330
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index 9546411bd790..3ba57429d9c4 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
3 out of 3 hunks ignored


DPDK STV team

                 reply	other threads:[~2017-03-16  0:02 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$11f25o2@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=pascal.mazon@6wind.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).