automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: santosh.shukla@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw29912 [PATCH v2 19/26] net/octeontx: add Rx queue setup and release ops
Date: 11 Oct 2017 08:52:01 -0700	[thread overview]
Message-ID: <1a8a4b$13stbii@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Date: Sun,  8 Oct 2017 18:14:20 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
                   Repo:dpdk-next-crypto, Branch:master, CommitID:f255b48dc3e66ca94c5bd60ce20f68ba0eb7f33e
                   Repo:dpdk-next-net, Branch:master, CommitID:1b2a708972a81acb6f8459fcce1b4cd8217e7c15
                   Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
                   Repo:dpdk, Branch:master, CommitID:d65b3b1668f2037745407c3909c43d85a18692a6
                   
Apply patch file failed:
Repo: dpdk-next-net
29912:
patching file drivers/net/octeontx/octeontx_ethdev.c
Hunk #1 succeeded at 1144 with fuzz 1 (offset 644 lines).
Hunk #2 FAILED at 676.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/octeontx/octeontx_ethdev.c.rej
patching file drivers/net/octeontx/octeontx_ethdev.h
Hunk #1 succeeded at 106 (offset 15 lines).


DPDK STV team

                 reply	other threads:[~2017-10-11 15:52 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='1a8a4b$13stbii@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=santosh.shukla@caviumnetworks.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).