From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw38055 [PATCH v2 2/2] net/mlx5: fix flow director mask
Date: 25 Apr 2018 22:13:02 -0700 [thread overview]
Message-ID: <ca5293$1fne2i@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38055
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Fri, 13 Apr 2018 17:28:50 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
Repo:dpdk-next-net, Branch:master, CommitID:b19ebcd718eed19760aff5100fe77b0c4a977eae
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:13573bd3f431934da373b1332ef92f8c30940272
Apply patch file failed:
Repo: dpdk
38055:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 2747 with fuzz 1 (offset 43 lines).
Hunk #3 FAILED at 2725.
Hunk #4 FAILED at 2750.
Hunk #5 FAILED at 2761.
Hunk #6 succeeded at 2776 with fuzz 2 (offset 4 lines).
Hunk #7 succeeded at 2804 with fuzz 2 (offset 19 lines).
3 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-crypto
38055:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 2747 with fuzz 1 (offset 43 lines).
Hunk #3 FAILED at 2725.
Hunk #4 FAILED at 2750.
Hunk #5 FAILED at 2761.
Hunk #6 succeeded at 2776 with fuzz 2 (offset 4 lines).
Hunk #7 succeeded at 2804 with fuzz 2 (offset 19 lines).
3 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-net
38055:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 2661.
Hunk #2 succeeded at 2734 with fuzz 2 (offset 33 lines).
Hunk #3 FAILED at 2722.
Hunk #4 succeeded at 2794 with fuzz 2 (offset 47 lines).
Hunk #5 succeeded at 2811 with fuzz 2 (offset 51 lines).
Hunk #6 succeeded at 2828 with fuzz 2 (offset 55 lines).
Hunk #7 succeeded at 2845 with fuzz 2 (offset 59 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-virtio
38055:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 2747 with fuzz 1 (offset 43 lines).
Hunk #3 FAILED at 2725.
Hunk #4 FAILED at 2750.
Hunk #5 FAILED at 2761.
Hunk #6 succeeded at 2776 with fuzz 2 (offset 4 lines).
Hunk #7 succeeded at 2804 with fuzz 2 (offset 19 lines).
3 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-eventdev
38055:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 2747 with fuzz 1 (offset 43 lines).
Hunk #3 FAILED at 2725.
Hunk #4 FAILED at 2750.
Hunk #5 FAILED at 2761.
Hunk #6 succeeded at 2776 with fuzz 2 (offset 4 lines).
Hunk #7 succeeded at 2804 with fuzz 2 (offset 19 lines).
3 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
DPDK STV team
reply other threads:[~2018-04-26 5:13 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='ca5293$1fne2i@fmsmga001.fm.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).