automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw62592[v2, 14/19] net/mlx5: extend flow mark support
Date: 09 Nov 2019 01:51:11 -0800	[thread overview]
Message-ID: <ee68f5$8hdtn1@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62592

_apply issues_

Submitter: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Date: 2019-11-06 17:37:48
Reply_mail: 1573061873-20898-15-git-send-email-viacheslavo@mellanox.com
DPDK git baseline:
	Repo:dpdk-next-net-mlx, CommitID: 685e0fbc4709ee94b17f5315cdf12fb942675423
	Repo:dpdk, CommitID: 6bbc5a9236250b708c6d1931e966c74da381b4f2

*Repo: dpdk-next-net-mlx
#define MLX5_FLOW_ITEM_TAG (1u << 18)

/* Pattern MISC bits. */
#define MLX5_FLOW_LAYER_ICMP (1u << 19)

error: patch failed: drivers/net/mlx5/mlx5_flow.h:102
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 1251 (offset 241 lines).
Hunk #2 succeeded at 2048 (offset 447 lines).
error: while searching for:
--
	};

	if (items == NULL)
		return -1;

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:3749
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
*Repo: dpdk
#define MLX5_FLOW_ITEM_TAG (1u << 18)

/* Pattern MISC bits. */
#define MLX5_FLOW_LAYER_ICMP (1u << 19)

error: patch failed: drivers/net/mlx5/mlx5_flow.h:102
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 805 (offset -205 lines).
error: while searching for:
	return 0;
--

/**
 * Validate SET_TAG action.
 *

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:1482
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2019-11-09  9:51 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='ee68f5$8hdtn1@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.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).