From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jasvinder.singh@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35913 [PATCH 35/37] ip_pipeline: add route example
Date: 13 Mar 2018 07:20:58 -0700 [thread overview]
Message-ID: <b11803$qd6d5@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/35913
_apply patch file failure_
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Fri, 9 Mar 2018 18:24:20 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Repo:dpdk-next-crypto, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Repo:dpdk-next-net, Branch:master, CommitID:fe6ff4e284f97e42eeabd9be29c9e49708395d58
Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
Repo:dpdk, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Apply patch file failed:
This patchset 35880-35915 apply failed on all repoes, please check error details at:
http://dpdk.org/patch/35900
http://dpdk.org/patch/35901
http://dpdk.org/patch/35902
http://dpdk.org/patch/35903
http://dpdk.org/patch/35904
http://dpdk.org/patch/35905
http://dpdk.org/patch/35906
http://dpdk.org/patch/35907
http://dpdk.org/patch/35908
http://dpdk.org/patch/35909
http://dpdk.org/patch/35892
http://dpdk.org/patch/35893
http://dpdk.org/patch/35890
http://dpdk.org/patch/35891
http://dpdk.org/patch/35896
http://dpdk.org/patch/35897
http://dpdk.org/patch/35894
http://dpdk.org/patch/35895
http://dpdk.org/patch/35889
http://dpdk.org/patch/35898
http://dpdk.org/patch/35899
DPDK STV team
reply other threads:[~2018-03-13 14:20 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$qd6d5@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jasvinder.singh@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).