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| pw27353 [PATCH v1 37/48] net/mlx4: clean up interrupt functions prototypes
Date: 01 Aug 2017 11:16:59 -0700	[thread overview]
Message-ID: <e624e2$12g5r73@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Tue,  1 Aug 2017 18:53:59 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:cb78ef9859ff68b9e260a844f151055ebd9ae78f
                   Repo:dpdk-next-crypto, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
                   Repo:dpdk-next-net, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
                   Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
                   Repo:dpdk, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
                   
Apply patch file failed:
Repo: dpdk
27353:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 3649 (offset 1601 lines).
Hunk #2 FAILED at 2076.
Hunk #3 succeeded at 3839 (offset 1660 lines).
Hunk #4 succeeded at 3904 (offset 1659 lines).
Hunk #5 succeeded at 4928 with fuzz 1 (offset 2194 lines).
Hunk #6 FAILED at 2776.
Hunk #7 FAILED at 2793.
Hunk #8 FAILED at 2854.
Hunk #9 succeeded at 5062 with fuzz 2 (offset 2193 lines).
Hunk #10 FAILED at 2886.
Hunk #11 FAILED at 2908.
Hunk #12 FAILED at 2924.
Hunk #13 FAILED at 2946.
Hunk #14 FAILED at 2980.
Hunk #15 FAILED at 3006.
10 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej

Repo: dpdk-next-crypto
27353:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 3649 (offset 1601 lines).
Hunk #2 FAILED at 2076.
Hunk #3 succeeded at 3839 (offset 1660 lines).
Hunk #4 succeeded at 3904 (offset 1659 lines).
Hunk #5 succeeded at 4928 with fuzz 1 (offset 2194 lines).
Hunk #6 FAILED at 2776.
Hunk #7 FAILED at 2793.
Hunk #8 FAILED at 2854.
Hunk #9 succeeded at 5062 with fuzz 2 (offset 2193 lines).
Hunk #10 FAILED at 2886.
Hunk #11 FAILED at 2908.
Hunk #12 FAILED at 2924.
Hunk #13 FAILED at 2946.
Hunk #14 FAILED at 2980.
Hunk #15 FAILED at 3006.
10 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej

Repo: dpdk-next-net
27353:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 3649 (offset 1601 lines).
Hunk #2 FAILED at 2076.
Hunk #3 succeeded at 3839 (offset 1660 lines).
Hunk #4 succeeded at 3904 (offset 1659 lines).
Hunk #5 succeeded at 4928 with fuzz 1 (offset 2194 lines).
Hunk #6 FAILED at 2776.
Hunk #7 FAILED at 2793.
Hunk #8 FAILED at 2854.
Hunk #9 succeeded at 5062 with fuzz 2 (offset 2193 lines).
Hunk #10 FAILED at 2886.
Hunk #11 FAILED at 2908.
Hunk #12 FAILED at 2924.
Hunk #13 FAILED at 2946.
Hunk #14 FAILED at 2980.
Hunk #15 FAILED at 3006.
10 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej

Repo: dpdk-next-virtio
27353:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 3649 (offset 1601 lines).
Hunk #2 FAILED at 2076.
Hunk #3 succeeded at 3839 (offset 1660 lines).
Hunk #4 succeeded at 3904 (offset 1659 lines).
Hunk #5 succeeded at 4928 with fuzz 1 (offset 2194 lines).
Hunk #6 FAILED at 2776.
Hunk #7 FAILED at 2793.
Hunk #8 FAILED at 2854.
Hunk #9 succeeded at 5062 with fuzz 2 (offset 2193 lines).
Hunk #10 FAILED at 2886.
Hunk #11 FAILED at 2908.
Hunk #12 FAILED at 2924.
Hunk #13 FAILED at 2946.
Hunk #14 FAILED at 2980.
Hunk #15 FAILED at 3006.
10 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej

Repo: dpdk-next-eventdev
27353:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 3649 (offset 1601 lines).
Hunk #2 FAILED at 2076.
Hunk #3 succeeded at 3839 (offset 1660 lines).
Hunk #4 succeeded at 3904 (offset 1659 lines).
Hunk #5 succeeded at 4928 with fuzz 1 (offset 2194 lines).
Hunk #6 FAILED at 2776.
Hunk #7 FAILED at 2793.
Hunk #8 FAILED at 2854.
Hunk #9 succeeded at 5062 with fuzz 2 (offset 2193 lines).
Hunk #10 FAILED at 2886.
Hunk #11 FAILED at 2908.
Hunk #12 FAILED at 2924.
Hunk #13 FAILED at 2946.
Hunk #14 FAILED at 2980.
Hunk #15 FAILED at 3006.
10 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej


DPDK STV team

                 reply	other threads:[~2017-08-01 18:17 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='e624e2$12g5r73@orsmga001.jf.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).