From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shahafs@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw40052 [PATCH] net/mlx5: fix default RSS level
Date: 16 May 2018 10:34:27 -0700 [thread overview]
Message-ID: <0590c7$1lr6g5@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2936 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/40052
_apply patch file failure_
Submitter: Shahaf Shuler <shahafs@mellanox.com>
Date: Tue, 15 May 2018 16:23:24 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:e0d88a394e91f446234aa04d0f9e01c150b0d347
Repo:dpdk-next-net, Branch:master, CommitID:08b7521c352952e4abe8cd6ed9e5e5084d5cfa9a
Repo:dpdk-next-virtio, Branch:master, CommitID:b88ef5968604fb493930fa221672a4258d107852
Repo:dpdk, Branch:master, CommitID:08b7521c352952e4abe8cd6ed9e5e5084d5cfa9a
Apply patch file failed:
Repo: dpdk
40052:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 773 (offset -32 lines).
Hunk #2 succeeded at 1117 (offset -49 lines).
Hunk #3 succeeded at 1749 (offset -49 lines).
Hunk #4 succeeded at 1821 (offset -49 lines).
Hunk #5 FAILED at 1947.
Hunk #6 FAILED at 2043.
Hunk #7 succeeded at 2342 (offset -150 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-crypto
40052:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 800 (offset -5 lines).
Hunk #2 succeeded at 1144 (offset -22 lines).
Hunk #3 succeeded at 1776 (offset -22 lines).
Hunk #4 succeeded at 1848 (offset -22 lines).
Hunk #5 FAILED at 1947.
Hunk #6 FAILED at 2043.
Hunk #7 succeeded at 2370 (offset -122 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-net
40052:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 773 (offset -32 lines).
Hunk #2 succeeded at 1117 (offset -49 lines).
Hunk #3 succeeded at 1749 (offset -49 lines).
Hunk #4 succeeded at 1821 (offset -49 lines).
Hunk #5 FAILED at 1947.
Hunk #6 FAILED at 2043.
Hunk #7 succeeded at 2342 (offset -150 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-virtio
40052:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 773 (offset -32 lines).
Hunk #2 succeeded at 1117 (offset -49 lines).
Hunk #3 succeeded at 1749 (offset -49 lines).
Hunk #4 succeeded at 1821 (offset -49 lines).
Hunk #5 FAILED at 1947.
Hunk #6 FAILED at 2043.
Hunk #7 succeeded at 2342 (offset -150 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-eventdev
40052:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 800 (offset -5 lines).
Hunk #2 succeeded at 1144 (offset -22 lines).
Hunk #3 succeeded at 1776 (offset -22 lines).
Hunk #4 succeeded at 1848 (offset -22 lines).
Hunk #5 FAILED at 1947.
Hunk #6 FAILED at 2043.
Hunk #7 succeeded at 2370 (offset -122 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
DPDK STV team
reply other threads:[~2018-05-16 17:34 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$1lr6g5@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=shahafs@mellanox.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).