automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Rasesh.Mody@cavium.com
Subject: [dpdk-test-report] |FAILURE| pw22259 [PATCH v3 53/61] net/qede/base: allow PMD to control vport and RSS engine ids
Date: 24 Mar 2017 22:04:23 -0700	[thread overview]
Message-ID: <e624e2$114f0of@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
Date: Fri, 24 Mar 2017 00:28:42 -0700
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:1df5f2222142242be872e47628a22e0bd0887a81
                   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
22259:
patching file drivers/net/qede/base/ecore_iov_api.h
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 401 (offset -16 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_iov_api.h.rej
patching file drivers/net/qede/base/ecore_sriov.c
Hunk #1 succeeded at 399 (offset -27 lines).
Hunk #2 succeeded at 427 (offset -27 lines).
Hunk #3 FAILED at 1015.
Hunk #4 succeeded at 2474 with fuzz 1 (offset -274 lines).
Hunk #5 succeeded at 3612 (offset -358 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_sriov.c.rej
patching file drivers/net/qede/base/ecore_sriov.h
Hunk #2 succeeded at 156 with fuzz 1.

Repo: dpdk-next-crypto
22259:
patching file drivers/net/qede/base/ecore_iov_api.h
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 401 (offset -16 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_iov_api.h.rej
patching file drivers/net/qede/base/ecore_sriov.c
Hunk #1 succeeded at 399 (offset -27 lines).
Hunk #2 succeeded at 427 (offset -27 lines).
Hunk #3 FAILED at 1015.
Hunk #4 succeeded at 2474 with fuzz 1 (offset -274 lines).
Hunk #5 succeeded at 3612 (offset -358 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_sriov.c.rej
patching file drivers/net/qede/base/ecore_sriov.h
Hunk #2 succeeded at 156 with fuzz 1.

Repo: dpdk-next-net
22259:
patching file drivers/net/qede/base/ecore_iov_api.h
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 401 (offset -16 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_iov_api.h.rej
patching file drivers/net/qede/base/ecore_sriov.c
Hunk #1 succeeded at 399 (offset -27 lines).
Hunk #2 succeeded at 427 (offset -27 lines).
Hunk #3 FAILED at 1015.
Hunk #4 succeeded at 2488 with fuzz 1 (offset -260 lines).
Hunk #5 succeeded at 3633 (offset -337 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_sriov.c.rej
patching file drivers/net/qede/base/ecore_sriov.h
Hunk #2 succeeded at 156 with fuzz 1.

Repo: dpdk-next-virtio
22259:
patching file drivers/net/qede/base/ecore_iov_api.h
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 401 (offset -16 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_iov_api.h.rej
patching file drivers/net/qede/base/ecore_sriov.c
Hunk #1 succeeded at 399 (offset -27 lines).
Hunk #2 succeeded at 427 (offset -27 lines).
Hunk #3 FAILED at 1015.
Hunk #4 succeeded at 2474 with fuzz 1 (offset -274 lines).
Hunk #5 succeeded at 3612 (offset -358 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_sriov.c.rej
patching file drivers/net/qede/base/ecore_sriov.h
Hunk #2 succeeded at 156 with fuzz 1.

Repo: dpdk-next-eventdev
22259:
patching file drivers/net/qede/base/ecore_iov_api.h
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 401 (offset -16 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_iov_api.h.rej
patching file drivers/net/qede/base/ecore_sriov.c
Hunk #1 succeeded at 399 (offset -27 lines).
Hunk #2 succeeded at 427 (offset -27 lines).
Hunk #3 FAILED at 1015.
Hunk #4 succeeded at 2474 with fuzz 1 (offset -274 lines).
Hunk #5 succeeded at 3612 (offset -358 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/qede/base/ecore_sriov.c.rej
patching file drivers/net/qede/base/ecore_sriov.h
Hunk #2 succeeded at 156 with fuzz 1.


DPDK STV team

             reply	other threads:[~2017-03-25  5:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25  5:04 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-25  4:30 sys_stv
2017-03-25  3:43 sys_stv
2017-03-25  2:58 sys_stv
2017-03-25  2:04 sys_stv
2017-03-25  1:26 sys_stv
2017-03-25  0:24 sys_stv
2017-03-25  0:04 sys_stv
2017-03-24 23:24 sys_stv
2017-03-24 22:43 sys_stv

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$114f0of@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=Rasesh.Mody@cavium.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).