From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw33246 [PATCH 1/6] net/mlx5: support tx swp tunnel offloading
Date: 15 Jan 2018 07:11:46 -0800 [thread overview]
Message-ID: <b11803$ae4j5@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3821 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33246
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Tue, 9 Jan 2018 22:11:10 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
Repo:dpdk-next-crypto, Branch:master, CommitID:95415cfefead276dff18262c9d96df73ecb3a8de
Repo:dpdk-next-net, Branch:master, CommitID:fb79a5525fb9d1979654f508c197a4f6186fcaaa
Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
Repo:dpdk, Branch:master, CommitID:bacbf5ac505a3063943e83196f7332fc6436a09e
Apply patch file failed:
Repo: dpdk
33246:
patching file drivers/net/mlx5/mlx5_prm.h
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #2 succeeded at 450 with fuzz 2.
Hunk #3 FAILED at 493.
Hunk #4 FAILED at 521.
Hunk #5 succeeded at 748 with fuzz 2 (offset 20 lines).
Hunk #6 succeeded at 757 (offset 20 lines).
Hunk #7 succeeded at 772 (offset 20 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 195 (offset -1 lines).
Hunk #2 FAILED at 624.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_txq.c
Hunk #1 FAILED at 729.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_txq.c.rej
Repo: dpdk-next-crypto
33246:
patching file drivers/net/mlx5/mlx5_prm.h
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #2 succeeded at 450 with fuzz 2.
Hunk #3 FAILED at 493.
Hunk #4 FAILED at 521.
Hunk #5 succeeded at 748 with fuzz 2 (offset 20 lines).
Hunk #6 succeeded at 757 (offset 20 lines).
Hunk #7 succeeded at 772 (offset 20 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 195 (offset -1 lines).
Hunk #2 FAILED at 624.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_txq.c
Hunk #1 FAILED at 729.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_txq.c.rej
Repo: dpdk-next-net
33246:
patching file drivers/net/mlx5/mlx5_prm.h
patching file drivers/net/mlx5/mlx5_rxtx.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 195 (offset -1 lines).
Hunk #2 FAILED at 624.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_txq.c
Repo: dpdk-next-virtio
33246:
patching file drivers/net/mlx5/mlx5_prm.h
patching file drivers/net/mlx5/mlx5_rxtx.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #2 FAILED at 624.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_txq.c
Hunk #1 FAILED at 729.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_txq.c.rej
Repo: dpdk-next-eventdev
33246:
patching file drivers/net/mlx5/mlx5_prm.h
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #2 succeeded at 450 with fuzz 2.
Hunk #3 FAILED at 493.
Hunk #4 FAILED at 521.
Hunk #5 succeeded at 748 with fuzz 2 (offset 20 lines).
Hunk #6 succeeded at 757 (offset 20 lines).
Hunk #7 succeeded at 772 (offset 20 lines).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 195 (offset -1 lines).
Hunk #2 FAILED at 624.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_txq.c
Hunk #1 FAILED at 729.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_txq.c.rej
DPDK STV team
reply other threads:[~2018-01-15 15:11 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='b11803$ae4j5@fmsmga002.fm.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).