From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw27378 [PATCH v1 12/21] net/mlx5: remove queue drop support
Date: 02 Aug 2017 08:41:55 -0700 [thread overview]
Message-ID: <ffb989$3h7iee@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4804 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27378
_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
27378:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 143.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 104 with fuzz 2 (offset 8 lines).
Hunk #2 succeeded at 280 (offset 7 lines).
Hunk #3 FAILED at 288.
Hunk #4 succeeded at 473 (offset -37 lines).
Hunk #5 FAILED at 616.
Hunk #6 FAILED at 1017.
Hunk #7 succeeded at 1210 (offset -29 lines).
Hunk #8 succeeded at 1266 (offset -29 lines).
Hunk #9 FAILED at 1315.
Hunk #10 succeeded at 1306 with fuzz 2 (offset -21 lines).
Hunk #11 FAILED at 1389.
Hunk #12 succeeded at 1505 (offset -13 lines).
Hunk #13 succeeded at 1528 (offset -13 lines).
5 out of 13 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-crypto
27378:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 143.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 104 with fuzz 2 (offset 8 lines).
Hunk #2 succeeded at 280 (offset 7 lines).
Hunk #3 FAILED at 288.
Hunk #4 succeeded at 473 (offset -37 lines).
Hunk #5 FAILED at 616.
Hunk #6 FAILED at 1017.
Hunk #7 succeeded at 1210 (offset -29 lines).
Hunk #8 succeeded at 1266 (offset -29 lines).
Hunk #9 FAILED at 1315.
Hunk #10 succeeded at 1306 with fuzz 2 (offset -21 lines).
Hunk #11 FAILED at 1389.
Hunk #12 succeeded at 1505 (offset -13 lines).
Hunk #13 succeeded at 1528 (offset -13 lines).
5 out of 13 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-net
27378:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 143.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 104 with fuzz 2 (offset 8 lines).
Hunk #2 succeeded at 280 (offset 7 lines).
Hunk #3 FAILED at 288.
Hunk #4 succeeded at 473 (offset -37 lines).
Hunk #5 FAILED at 616.
Hunk #6 FAILED at 1017.
Hunk #7 succeeded at 1210 (offset -29 lines).
Hunk #8 succeeded at 1266 (offset -29 lines).
Hunk #9 FAILED at 1315.
Hunk #10 succeeded at 1306 with fuzz 2 (offset -21 lines).
Hunk #11 FAILED at 1389.
Hunk #12 succeeded at 1505 (offset -13 lines).
Hunk #13 succeeded at 1528 (offset -13 lines).
5 out of 13 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-virtio
27378:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 143.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 104 with fuzz 2 (offset 8 lines).
Hunk #2 succeeded at 280 (offset 7 lines).
Hunk #3 FAILED at 288.
Hunk #4 succeeded at 473 (offset -37 lines).
Hunk #5 FAILED at 616.
Hunk #6 FAILED at 1017.
Hunk #7 succeeded at 1210 (offset -29 lines).
Hunk #8 succeeded at 1266 (offset -29 lines).
Hunk #9 FAILED at 1315.
Hunk #10 succeeded at 1306 with fuzz 2 (offset -21 lines).
Hunk #11 FAILED at 1389.
Hunk #12 succeeded at 1505 (offset -13 lines).
Hunk #13 succeeded at 1528 (offset -13 lines).
5 out of 13 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-eventdev
27378:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 143.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 104 with fuzz 2 (offset 8 lines).
Hunk #2 succeeded at 280 (offset 7 lines).
Hunk #3 FAILED at 288.
Hunk #4 succeeded at 473 (offset -37 lines).
Hunk #5 FAILED at 616.
Hunk #6 FAILED at 1017.
Hunk #7 succeeded at 1210 (offset -29 lines).
Hunk #8 succeeded at 1266 (offset -29 lines).
Hunk #9 FAILED at 1315.
Hunk #10 succeeded at 1306 with fuzz 2 (offset -21 lines).
Hunk #11 FAILED at 1389.
Hunk #12 succeeded at 1505 (offset -13 lines).
Hunk #13 succeeded at 1528 (offset -13 lines).
5 out of 13 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
DPDK STV team
next reply other threads:[~2017-08-02 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:41 sys_stv [this message]
2017-08-03 6:13 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$3h7iee@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).