automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ajit.khaparde@broadcom.com
Subject: [dpdk-test-report] |FAILURE| pw24669 [PATCH v2 16/25] bnxt: add support for led on/off
Date: 27 May 2017 04:58:12 -0700	[thread overview]
Message-ID: <e81775$12c3drn@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Fri, 26 May 2017 13:39:32 -0500
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:776003f4a8e7af4f98338983eb2dfe0a52e8eaf5
                   Repo:dpdk-next-crypto, Branch:master, CommitID:0766a55d35be8d3d5fe9d1858bb5c3ab648617ce
                   Repo:dpdk-next-net, Branch:master, CommitID:8c79ce3907c395eb5af49b58431c95bf1746857e
                   Repo:dpdk-next-virtio, Branch:master, CommitID:1ee9702c260bbd4a282efdeaa7277ddbfc87177a
                   Repo:dpdk, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
                   
Apply patch file failed:
Repo: dpdk
24669:
patching file drivers/net/bnxt/bnxt.h
Hunk #1 succeeded at 46 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 241.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt.h.rej
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 1003 with fuzz 1 (offset -494 lines).
Hunk #2 FAILED at 1558.
Hunk #3 FAILED at 1831.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 1532 with fuzz 1 (offset -921 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/hsi_struct_def_dpdk.h
Hunk #1 succeeded at 3704 (offset -2039 lines).

Repo: dpdk-next-crypto
24669:
patching file drivers/net/bnxt/bnxt.h
Hunk #1 succeeded at 46 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 241.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt.h.rej
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 1003 with fuzz 1 (offset -494 lines).
Hunk #2 FAILED at 1558.
Hunk #3 FAILED at 1831.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 1532 with fuzz 1 (offset -921 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/hsi_struct_def_dpdk.h
Hunk #1 succeeded at 3704 (offset -2039 lines).

Repo: dpdk-next-net
24669:
patching file drivers/net/bnxt/bnxt.h
Hunk #1 succeeded at 46 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 241.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt.h.rej
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 1003 with fuzz 1 (offset -494 lines).
Hunk #2 FAILED at 1558.
Hunk #3 FAILED at 1831.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 1532 with fuzz 1 (offset -921 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/hsi_struct_def_dpdk.h
Hunk #1 succeeded at 3704 (offset -2039 lines).

Repo: dpdk-next-virtio
24669:
patching file drivers/net/bnxt/bnxt.h
Hunk #1 succeeded at 46 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 241.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt.h.rej
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 1003 with fuzz 1 (offset -494 lines).
Hunk #2 FAILED at 1558.
Hunk #3 FAILED at 1831.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 1532 with fuzz 1 (offset -921 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/hsi_struct_def_dpdk.h
Hunk #1 succeeded at 3704 (offset -2039 lines).

Repo: dpdk-next-eventdev
24669:
patching file drivers/net/bnxt/bnxt.h
Hunk #1 succeeded at 46 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 241.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt.h.rej
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 1003 with fuzz 1 (offset -494 lines).
Hunk #2 FAILED at 1558.
Hunk #3 FAILED at 1831.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 1532 with fuzz 1 (offset -921 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/hsi_struct_def_dpdk.h
Hunk #1 succeeded at 3704 (offset -2039 lines).


DPDK STV team

                 reply	other threads:[~2017-05-27 11:58 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$12c3drn@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ajit.khaparde@broadcom.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).