[dpdk-test-report] |FAILURE| pw30261 [PATCH v2 10/29] net/mlx4: merge flow creation and validation code

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| pw30261 [PATCH v2 10/29] net/mlx4: merge flow creation and validation code
Date: 13 Oct 2017 07:56:50 -0700	[thread overview]
Message-ID: <1a8a4b$13tlbki@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 12 Oct 2017 14:19:24 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
                   Repo:dpdk-next-crypto, Branch:master, CommitID:84e0ded38ac5564f89576843466e2385128c83f2
                   Repo:dpdk-next-net, Branch:master, CommitID:8c49d5f1c219d986bb129c61dfa2e155d7f2b1da
                   Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
                   Repo:dpdk, Branch:master, CommitID:a8ea1e5fb64786065776491cec721b16d100171a
                   
Apply patch file failed:
Repo: dpdk
30261:
patching file drivers/net/mlx4/mlx4_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
25 out of 25 hunks ignored -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.h.rej

Repo: dpdk-next-crypto
30261:
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #2 FAILED at 111.
Hunk #3 FAILED at 138.
Hunk #4 succeeded at 162 (offset 9 lines).
Hunk #5 FAILED at 184.
Hunk #6 FAILED at 215.
Hunk #7 succeeded at 240 (offset 11 lines).
Hunk #8 FAILED at 260.
Hunk #9 succeeded at 286 (offset 12 lines).
Hunk #10 FAILED at 301.
Hunk #11 succeeded at 328 (offset 13 lines).
Hunk #12 succeeded at 579 (offset 22 lines).
Hunk #13 FAILED at 570.
Hunk #14 FAILED at 605.
Hunk #15 FAILED at 635.
Hunk #16 FAILED at 647.
Hunk #17 FAILED at 660.
Hunk #18 FAILED at 699.
Hunk #19 FAILED at 778.
Hunk #20 FAILED at 847.
Hunk #21 succeeded at 965 (offset 24 lines).
Hunk #22 succeeded at 975 (offset 24 lines).
Hunk #23 succeeded at 1007 (offset 24 lines).
Hunk #24 succeeded at 1020 (offset 24 lines).
Hunk #25 succeeded at 1046 (offset 24 lines).
14 out of 25 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.h.rej

Repo: dpdk-next-net
30261:
patching file drivers/net/mlx4/mlx4_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
25 out of 25 hunks ignored -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.h.rej

Repo: dpdk-next-virtio
30261:
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #2 FAILED at 111.
Hunk #3 FAILED at 138.
Hunk #4 succeeded at 162 (offset 9 lines).
Hunk #5 FAILED at 184.
Hunk #6 FAILED at 215.
Hunk #7 succeeded at 240 (offset 11 lines).
Hunk #8 FAILED at 260.
Hunk #9 succeeded at 286 (offset 12 lines).
Hunk #10 FAILED at 301.
Hunk #11 succeeded at 328 (offset 13 lines).
Hunk #12 succeeded at 579 (offset 22 lines).
Hunk #13 FAILED at 570.
Hunk #14 FAILED at 605.
Hunk #15 FAILED at 635.
Hunk #16 FAILED at 647.
Hunk #17 FAILED at 660.
Hunk #18 FAILED at 699.
Hunk #19 FAILED at 778.
Hunk #20 FAILED at 847.
Hunk #21 succeeded at 965 (offset 24 lines).
Hunk #22 succeeded at 975 (offset 24 lines).
Hunk #23 succeeded at 1007 (offset 24 lines).
Hunk #24 succeeded at 1020 (offset 24 lines).
Hunk #25 succeeded at 1046 (offset 24 lines).
14 out of 25 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.h.rej

Repo: dpdk-next-eventdev
30261:
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #2 FAILED at 111.
Hunk #3 FAILED at 138.
Hunk #4 succeeded at 162 (offset 9 lines).
Hunk #5 FAILED at 184.
Hunk #6 FAILED at 215.
Hunk #7 succeeded at 240 (offset 11 lines).
Hunk #8 FAILED at 260.
Hunk #9 succeeded at 286 (offset 12 lines).
Hunk #10 FAILED at 301.
Hunk #11 succeeded at 328 (offset 13 lines).
Hunk #12 succeeded at 579 (offset 22 lines).
Hunk #13 FAILED at 570.
Hunk #14 FAILED at 605.
Hunk #15 FAILED at 635.
Hunk #16 FAILED at 647.
Hunk #17 FAILED at 660.
Hunk #18 FAILED at 699.
Hunk #19 FAILED at 778.
Hunk #20 FAILED at 847.
Hunk #21 succeeded at 965 (offset 24 lines).
Hunk #22 succeeded at 975 (offset 24 lines).
Hunk #23 succeeded at 1007 (offset 24 lines).
Hunk #24 succeeded at 1020 (offset 24 lines).
Hunk #25 succeeded at 1046 (offset 24 lines).
14 out of 25 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.h.rej


DPDK STV team

                 reply	other threads:[~2017-10-13 14:56 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$13tlbki@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).