From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw29714 [PATCH v2 22/30] net/mlx5: fully convert a flow to verbs in validate
Date: 05 Oct 2017 11:58:10 -0700 [thread overview]
Message-ID: <8a7c36$134egm3@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29714
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Thu, 5 Oct 2017 14:50:00 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b4b3260b63d2d8d76ff1c66ab4b70e6d1b6a4bbe
Repo:dpdk-next-crypto, Branch:master, CommitID:674d3663fb31c881d38f7d86e4a906751053dce1
Repo:dpdk-next-net, Branch:master, CommitID:4fb81ce17f9c23d9cdf6453652e1cfcbb0743763
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:0a10db80bca3262977646f814e913f4af0b627cc
Apply patch file failed:
Repo: dpdk
29714:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 286 with fuzz 2 (offset -21 lines).
Hunk #2 succeeded at 405 (offset -14 lines).
Hunk #3 succeeded at 424 (offset -14 lines).
Hunk #4 FAILED at 656.
Hunk #5 succeeded at 1015 with fuzz 2 (offset -10 lines).
Hunk #6 succeeded at 1023 (offset -10 lines).
Hunk #7 succeeded at 1199 (offset 21 lines).
Hunk #8 FAILED at 1190.
Hunk #9 FAILED at 1231.
3 out of 9 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-crypto
29714:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 286 with fuzz 2 (offset -21 lines).
Hunk #2 succeeded at 405 (offset -14 lines).
Hunk #3 succeeded at 424 (offset -14 lines).
Hunk #4 FAILED at 656.
Hunk #5 succeeded at 1015 with fuzz 2 (offset -10 lines).
Hunk #6 succeeded at 1023 (offset -10 lines).
Hunk #7 succeeded at 1199 (offset 21 lines).
Hunk #8 FAILED at 1190.
Hunk #9 FAILED at 1231.
3 out of 9 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-virtio
29714:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 286 with fuzz 2 (offset -21 lines).
Hunk #2 succeeded at 405 (offset -14 lines).
Hunk #3 succeeded at 424 (offset -14 lines).
Hunk #4 FAILED at 656.
Hunk #5 succeeded at 1015 with fuzz 2 (offset -10 lines).
Hunk #6 succeeded at 1023 (offset -10 lines).
Hunk #7 succeeded at 1199 (offset 21 lines).
Hunk #8 FAILED at 1190.
Hunk #9 FAILED at 1231.
3 out of 9 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
Repo: dpdk-next-eventdev
29714:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 286 with fuzz 2 (offset -21 lines).
Hunk #2 succeeded at 405 (offset -14 lines).
Hunk #3 succeeded at 424 (offset -14 lines).
Hunk #4 FAILED at 656.
Hunk #5 succeeded at 1015 with fuzz 2 (offset -10 lines).
Hunk #6 succeeded at 1023 (offset -10 lines).
Hunk #7 succeeded at 1199 (offset 21 lines).
Hunk #8 FAILED at 1190.
Hunk #9 FAILED at 1231.
3 out of 9 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
DPDK STV team
reply other threads:[~2017-10-05 18:58 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='8a7c36$134egm3@orsmga001.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).