From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw38010 [PATCH v3 08/14] net/mlx5: add hardware flow debug dump
Date: 25 Apr 2018 11:12:02 -0700 [thread overview]
Message-ID: <0590c7$1gdub3@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3509 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38010
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Fri, 13 Apr 2018 19:20:17 +0800
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:ad9dabca15e9e7a61361fe0826d138c06f9d9832
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:13573bd3f431934da373b1332ef92f8c30940272
Apply patch file failed:
Repo: dpdk
38010:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 2072 (offset 23 lines).
Hunk #2 succeeded at 2164 (offset 23 lines).
Hunk #3 succeeded at 2172 (offset 23 lines).
Hunk #4 succeeded at 2678 with fuzz 2 (offset -14 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #3 succeeded at 1442 (offset -6 lines).
Hunk #4 FAILED at 1475.
Hunk #5 succeeded at 1573 (offset -13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_utils.h
Repo: dpdk-next-crypto
38010:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 2072 (offset 23 lines).
Hunk #2 succeeded at 2164 (offset 23 lines).
Hunk #3 succeeded at 2172 (offset 23 lines).
Hunk #4 succeeded at 2678 with fuzz 2 (offset -14 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #3 succeeded at 1442 (offset -6 lines).
Hunk #4 FAILED at 1475.
Hunk #5 succeeded at 1573 (offset -13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_utils.h
Repo: dpdk-next-net
38010:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 2091 (offset 42 lines).
Hunk #2 succeeded at 2183 (offset 42 lines).
Hunk #3 succeeded at 2191 (offset 42 lines).
Hunk #4 succeeded at 2697 with fuzz 2 (offset 5 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #3 succeeded at 1442 (offset -6 lines).
Hunk #4 FAILED at 1475.
Hunk #5 succeeded at 1573 (offset -13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_utils.h
Repo: dpdk-next-virtio
38010:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 2072 (offset 23 lines).
Hunk #2 succeeded at 2164 (offset 23 lines).
Hunk #3 succeeded at 2172 (offset 23 lines).
Hunk #4 succeeded at 2678 with fuzz 2 (offset -14 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #3 succeeded at 1442 (offset -6 lines).
Hunk #4 FAILED at 1475.
Hunk #5 succeeded at 1573 (offset -13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_utils.h
Repo: dpdk-next-eventdev
38010:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 2072 (offset 23 lines).
Hunk #2 succeeded at 2164 (offset 23 lines).
Hunk #3 succeeded at 2172 (offset 23 lines).
Hunk #4 succeeded at 2678 with fuzz 2 (offset -14 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #3 succeeded at 1442 (offset -6 lines).
Hunk #4 FAILED at 1475.
Hunk #5 succeeded at 1573 (offset -13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_utils.h
DPDK STV team
reply other threads:[~2018-04-25 18:12 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='0590c7$1gdub3@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@mellanox.com \
/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).