From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw38340 [PATCH v4 01/11] net/mlx5: support 16 hardware priorities
Date: 28 Apr 2018 16:35:04 -0700 [thread overview]
Message-ID: <f7a79a$1jtpou@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3592 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38340
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Tue, 17 Apr 2018 23:14:34 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:996096e629c3b6d08eab4acf51122ff783350b39
Repo:dpdk-next-net, Branch:master, CommitID:1a7dc2252f2862d8c783d114ab97ed490de8d160
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Apply patch file failed:
Repo: dpdk
38340:
patching file drivers/net/mlx5/mlx5.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 89.
Hunk #2 succeeded at 111 with fuzz 2 (offset 6 lines).
Hunk #3 FAILED at 256.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
10 out of 10 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_trigger.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
Repo: dpdk-next-net
38340:
patching file drivers/net/mlx5/mlx5.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 89.
Hunk #2 succeeded at 111 with fuzz 2 (offset 6 lines).
Hunk #3 FAILED at 256.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
10 out of 10 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_trigger.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
Repo: dpdk-next-eventdev
38340:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 193 (offset -4 lines).
Hunk #2 succeeded at 608 (offset -12 lines).
Hunk #3 succeeded at 972 with fuzz 1 (offset -36 lines).
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 89.
Hunk #2 succeeded at 103 (offset -2 lines).
Hunk #3 succeeded at 249 (offset -7 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 27 (offset -4 lines).
Hunk #2 succeeded at 124 (offset -4 lines).
Hunk #3 succeeded at 133 (offset -4 lines).
Hunk #4 succeeded at 141 (offset -4 lines).
Hunk #5 succeeded at 150 (offset -4 lines).
Hunk #6 succeeded at 159 (offset -4 lines).
Hunk #7 succeeded at 167 (offset -4 lines).
Hunk #8 succeeded at 895 (offset -4 lines).
Hunk #9 succeeded at 1173 (offset -4 lines).
Hunk #10 succeeded at 3157 (offset -21 lines).
patching file drivers/net/mlx5/mlx5_trigger.c
DPDK STV team
reply other threads:[~2018-04-28 23:35 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='f7a79a$1jtpou@orsmga002.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).