automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw27367 [PATCH v1 01/21] net/mlx5: merge action and flow parser structure
Date: 02 Aug 2017 08:03:38 -0700	[thread overview]
Message-ID: <ffb989$3h72sl@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Wed,  2 Aug 2017 16:10:26 +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
27367:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 278 (offset 7 lines).
Hunk #2 succeeded at 305 (offset 7 lines).
Hunk #3 succeeded at 383 (offset 7 lines).
Hunk #4 succeeded at 393 (offset 7 lines).
Hunk #5 succeeded at 475 (offset 7 lines).
Hunk #6 succeeded at 485 (offset 7 lines).
Hunk #7 succeeded at 499 (offset 7 lines).
Hunk #8 succeeded at 516 (offset 7 lines).
Hunk #9 succeeded at 546 (offset 7 lines).
Hunk #10 FAILED at 562.
Hunk #11 succeeded at 614 (offset 9 lines).
Hunk #12 succeeded at 645 (offset 9 lines).
Hunk #13 succeeded at 694 (offset 9 lines).
Hunk #14 succeeded at 726 (offset 9 lines).
Hunk #15 succeeded at 780 (offset 9 lines).
Hunk #16 succeeded at 837 (offset 9 lines).
Hunk #17 succeeded at 881 (offset 9 lines).
Hunk #18 succeeded at 925 (offset 9 lines).
Hunk #19 succeeded at 964 (offset 9 lines).
Hunk #20 succeeded at 994 (offset 9 lines).
Hunk #21 succeeded at 1046 (offset 13 lines).
Hunk #22 succeeded at 1054 (offset 13 lines).
Hunk #23 succeeded at 1175 (offset 13 lines).
Hunk #24 succeeded at 1207 (offset 13 lines).
1 out of 24 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej

Repo: dpdk-next-crypto
27367:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 278 (offset 7 lines).
Hunk #2 succeeded at 305 (offset 7 lines).
Hunk #3 succeeded at 383 (offset 7 lines).
Hunk #4 succeeded at 393 (offset 7 lines).
Hunk #5 succeeded at 475 (offset 7 lines).
Hunk #6 succeeded at 485 (offset 7 lines).
Hunk #7 succeeded at 499 (offset 7 lines).
Hunk #8 succeeded at 516 (offset 7 lines).
Hunk #9 succeeded at 546 (offset 7 lines).
Hunk #10 FAILED at 562.
Hunk #11 succeeded at 614 (offset 9 lines).
Hunk #12 succeeded at 645 (offset 9 lines).
Hunk #13 succeeded at 694 (offset 9 lines).
Hunk #14 succeeded at 726 (offset 9 lines).
Hunk #15 succeeded at 780 (offset 9 lines).
Hunk #16 succeeded at 837 (offset 9 lines).
Hunk #17 succeeded at 881 (offset 9 lines).
Hunk #18 succeeded at 925 (offset 9 lines).
Hunk #19 succeeded at 964 (offset 9 lines).
Hunk #20 succeeded at 994 (offset 9 lines).
Hunk #21 succeeded at 1046 (offset 13 lines).
Hunk #22 succeeded at 1054 (offset 13 lines).
Hunk #23 succeeded at 1175 (offset 13 lines).
Hunk #24 succeeded at 1207 (offset 13 lines).
1 out of 24 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej

Repo: dpdk-next-net
27367:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 278 (offset 7 lines).
Hunk #2 succeeded at 305 (offset 7 lines).
Hunk #3 succeeded at 383 (offset 7 lines).
Hunk #4 succeeded at 393 (offset 7 lines).
Hunk #5 succeeded at 475 (offset 7 lines).
Hunk #6 succeeded at 485 (offset 7 lines).
Hunk #7 succeeded at 499 (offset 7 lines).
Hunk #8 succeeded at 516 (offset 7 lines).
Hunk #9 succeeded at 546 (offset 7 lines).
Hunk #10 FAILED at 562.
Hunk #11 succeeded at 614 (offset 9 lines).
Hunk #12 succeeded at 645 (offset 9 lines).
Hunk #13 succeeded at 694 (offset 9 lines).
Hunk #14 succeeded at 726 (offset 9 lines).
Hunk #15 succeeded at 780 (offset 9 lines).
Hunk #16 succeeded at 837 (offset 9 lines).
Hunk #17 succeeded at 881 (offset 9 lines).
Hunk #18 succeeded at 925 (offset 9 lines).
Hunk #19 succeeded at 964 (offset 9 lines).
Hunk #20 succeeded at 994 (offset 9 lines).
Hunk #21 succeeded at 1046 (offset 13 lines).
Hunk #22 succeeded at 1054 (offset 13 lines).
Hunk #23 succeeded at 1175 (offset 13 lines).
Hunk #24 succeeded at 1207 (offset 13 lines).
1 out of 24 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej

Repo: dpdk-next-virtio
27367:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 278 (offset 7 lines).
Hunk #2 succeeded at 305 (offset 7 lines).
Hunk #3 succeeded at 383 (offset 7 lines).
Hunk #4 succeeded at 393 (offset 7 lines).
Hunk #5 succeeded at 475 (offset 7 lines).
Hunk #6 succeeded at 485 (offset 7 lines).
Hunk #7 succeeded at 499 (offset 7 lines).
Hunk #8 succeeded at 516 (offset 7 lines).
Hunk #9 succeeded at 546 (offset 7 lines).
Hunk #10 FAILED at 562.
Hunk #11 succeeded at 614 (offset 9 lines).
Hunk #12 succeeded at 645 (offset 9 lines).
Hunk #13 succeeded at 694 (offset 9 lines).
Hunk #14 succeeded at 726 (offset 9 lines).
Hunk #15 succeeded at 780 (offset 9 lines).
Hunk #16 succeeded at 837 (offset 9 lines).
Hunk #17 succeeded at 881 (offset 9 lines).
Hunk #18 succeeded at 925 (offset 9 lines).
Hunk #19 succeeded at 964 (offset 9 lines).
Hunk #20 succeeded at 994 (offset 9 lines).
Hunk #21 succeeded at 1046 (offset 13 lines).
Hunk #22 succeeded at 1054 (offset 13 lines).
Hunk #23 succeeded at 1175 (offset 13 lines).
Hunk #24 succeeded at 1207 (offset 13 lines).
1 out of 24 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej

Repo: dpdk-next-eventdev
27367:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 278 (offset 7 lines).
Hunk #2 succeeded at 305 (offset 7 lines).
Hunk #3 succeeded at 383 (offset 7 lines).
Hunk #4 succeeded at 393 (offset 7 lines).
Hunk #5 succeeded at 475 (offset 7 lines).
Hunk #6 succeeded at 485 (offset 7 lines).
Hunk #7 succeeded at 499 (offset 7 lines).
Hunk #8 succeeded at 516 (offset 7 lines).
Hunk #9 succeeded at 546 (offset 7 lines).
Hunk #10 FAILED at 562.
Hunk #11 succeeded at 614 (offset 9 lines).
Hunk #12 succeeded at 645 (offset 9 lines).
Hunk #13 succeeded at 694 (offset 9 lines).
Hunk #14 succeeded at 726 (offset 9 lines).
Hunk #15 succeeded at 780 (offset 9 lines).
Hunk #16 succeeded at 837 (offset 9 lines).
Hunk #17 succeeded at 881 (offset 9 lines).
Hunk #18 succeeded at 925 (offset 9 lines).
Hunk #19 succeeded at 964 (offset 9 lines).
Hunk #20 succeeded at 994 (offset 9 lines).
Hunk #21 succeeded at 1046 (offset 13 lines).
Hunk #22 succeeded at 1054 (offset 13 lines).
Hunk #23 succeeded at 1175 (offset 13 lines).
Hunk #24 succeeded at 1207 (offset 13 lines).
1 out of 24 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej


DPDK STV team

             reply	other threads:[~2017-08-02 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 15:03 sys_stv [this message]
2017-08-03  5:47 sys_stv

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='ffb989$3h72sl@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=nelio.laranjeiro@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).