From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw43008[v2, 3/6] net/mlx5: add fate actions to switch flow rules
Date: 13 Jul 2018 02:46:21 -0700 [thread overview]
Message-ID: <0590c7$252hvp@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/43008
_apply issues_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: 2018-07-13 09:40:41
DPDK git baseline:
Repo:dpdk-master, CommitID: 0b82bd7b24c95ddd77f8e0b93df8456e1a38d627
Repo:dpdk-next-eventdev, CommitID: 9131a10a60bdbf8cd19e0158c6e01648a1d25e23
Repo:dpdk-next-net, CommitID: e5647516deae231db94b5488a6c3d48310ab619c
Repo:dpdk-next-crypto, CommitID: ed3077c16557e40e1967bed146eed3023b6cea5f
Repo:dpdk-next-virtio, CommitID: 3afaf9bf05f701c170ffe90a6b3365bbb3738e9d
*Repo: dpdk-master
Checking patch drivers/net/mlx5/mlx5_nl_flow.c...
error: drivers/net/mlx5/mlx5_nl_flow.c: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch drivers/net/mlx5/mlx5_nl_flow.c...
error: drivers/net/mlx5/mlx5_nl_flow.c: No such file or directory
*Repo: dpdk-next-net
Checking patch drivers/net/mlx5/mlx5_nl_flow.c...
error: drivers/net/mlx5/mlx5_nl_flow.c: No such file or directory
*Repo: dpdk-next-crypto
Checking patch drivers/net/mlx5/mlx5_nl_flow.c...
error: drivers/net/mlx5/mlx5_nl_flow.c: No such file or directory
*Repo: dpdk-next-virtio
Checking patch drivers/net/mlx5/mlx5_nl_flow.c...
error: drivers/net/mlx5/mlx5_nl_flow.c: No such file or directory
DPDK STV team
reply other threads:[~2018-07-13 9:46 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$252hvp@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).