automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw31131 [PATCH 2/2] net/mlx4: share memory region resources
Date: 02 Nov 2017 12:24:22 -0700	[thread overview]
Message-ID: <1a8a4b$1459qtq@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 2 Nov 2017 19:14:22 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b96273bb75fbd99a9732aa4d49658a3525b225b0
                   Repo:dpdk-next-crypto, Branch:master, CommitID:289ba0c0f52a6577fd324f4b47bbde58d17305be
                   Repo:dpdk-next-net, Branch:master, CommitID:21eed242557cbe6f9620f2f07390fb65059962cc
                   Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
                   Repo:dpdk, Branch:master, CommitID:6fb00f8baefa03b9cfd1b2dfc1787258b8459601
                   
Apply patch file failed:
Repo: dpdk
31131:
patching file drivers/net/mlx4/mlx4.h
Hunk #4 FAILED at 174.
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 52 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 FAILED at 182.
Hunk #4 FAILED at 208.
Hunk #5 FAILED at 224.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_mr.c.rej
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c

Repo: dpdk-next-crypto
31131:
patching file drivers/net/mlx4/mlx4.h
Hunk #4 FAILED at 174.
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 52 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 FAILED at 182.
Hunk #4 FAILED at 208.
Hunk #5 FAILED at 224.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_mr.c.rej
patching file drivers/net/mlx4/mlx4_rxq.c
Hunk #1 succeeded at 799 (offset -5 lines).
Hunk #2 succeeded at 863 (offset -5 lines).
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c

Repo: dpdk-next-net
31131:
patching file drivers/net/mlx4/mlx4.h
Hunk #4 FAILED at 174.
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 52 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 FAILED at 182.
Hunk #4 FAILED at 208.
Hunk #5 FAILED at 224.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_mr.c.rej
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c

Repo: dpdk-next-virtio
31131:
patching file drivers/net/mlx4/mlx4.h
Hunk #4 FAILED at 174.
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 52 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 FAILED at 182.
Hunk #4 FAILED at 208.
Hunk #5 FAILED at 224.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_mr.c.rej
patching file drivers/net/mlx4/mlx4_rxq.c
Hunk #1 succeeded at 526 (offset -278 lines).
Hunk #2 succeeded at 665 (offset -203 lines).
patching file drivers/net/mlx4/mlx4_rxtx.h
Hunk #2 succeeded at 133 (offset -1 lines).
patching file drivers/net/mlx4/mlx4_txq.c

Repo: dpdk-next-eventdev
31131:
patching file drivers/net/mlx4/mlx4.h
Hunk #4 FAILED at 174.
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 52 with fuzz 2 (offset -3 lines).
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 FAILED at 182.
Hunk #4 FAILED at 208.
Hunk #5 FAILED at 224.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_mr.c.rej
patching file drivers/net/mlx4/mlx4_rxq.c
Hunk #1 succeeded at 526 (offset -278 lines).
Hunk #2 succeeded at 665 (offset -203 lines).
patching file drivers/net/mlx4/mlx4_rxtx.h
Hunk #2 succeeded at 133 (offset -1 lines).
patching file drivers/net/mlx4/mlx4_txq.c


DPDK STV team

                 reply	other threads:[~2017-11-02 19:24 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$1459qtq@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=adrien.mazarguil@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).