From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw4379618.08 build error on ppc64el - bool as vector type
Date: 21 Aug 2018 07:27:06 -0700 [thread overview]
Message-ID: <0590c7$2fon2m@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/43796
_apply issues_
Submitter: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: 2018-08-21 14:19:54
DPDK git baseline:
Repo:dpdk-master, CommitID: 7281cf520f890a5e779596c872e2440af7131eae
Repo:dpdk-next-eventdev, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
Repo:dpdk-next-net, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
Repo:dpdk-next-crypto, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
Repo:dpdk-next-virtio, CommitID: 385ba3e1096528bf1cc3afd2d66773330610ccad
*Repo: dpdk-master
Repo:dpdk-master, CommitID: 7281cf520f890a5e779596c872e2440af7131eae
fatal: patch fragment without header at line 71: @@ -862,7 +862,7 @@ mlx5_nl_switch_info_cb(struct nlmsghdr *nh, void *arg)
*Repo: dpdk-next-eventdev
Repo:dpdk-next-eventdev, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
fatal: patch fragment without header at line 71: @@ -862,7 +862,7 @@ mlx5_nl_switch_info_cb(struct nlmsghdr *nh, void *arg)
*Repo: dpdk-next-net
Repo:dpdk-next-net, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
fatal: patch fragment without header at line 71: @@ -862,7 +862,7 @@ mlx5_nl_switch_info_cb(struct nlmsghdr *nh, void *arg)
*Repo: dpdk-next-crypto
Repo:dpdk-next-crypto, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
fatal: patch fragment without header at line 71: @@ -862,7 +862,7 @@ mlx5_nl_switch_info_cb(struct nlmsghdr *nh, void *arg)
*Repo: dpdk-next-virtio
Repo:dpdk-next-virtio, CommitID: 385ba3e1096528bf1cc3afd2d66773330610ccad
fatal: patch fragment without header at line 71: @@ -862,7 +862,7 @@ mlx5_nl_switch_info_cb(struct nlmsghdr *nh, void *arg)
DPDK STV team
reply other threads:[~2018-08-21 14:30 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$2fon2m@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).