From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw24108 [PATCH v2] app/testpmd: disable latency stats by default
Date: 04 May 2017 17:25:56 -0700 [thread overview]
Message-ID: <63cbe6$12mr1oj@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24108
_apply patch file failure_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Thu, 4 May 2017 17:28:48 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:70a969503bfcc2e8b0dd9fa71dae310c5358c9bc
Repo:dpdk-next-net, Branch:master, CommitID:70a969503bfcc2e8b0dd9fa71dae310c5358c9bc
Repo:dpdk-next-virtio, Branch:master, CommitID:ad06857e40c3d30f92ede00e840bbd8e6a69b703
Repo:dpdk, Branch:master, CommitID:5b923dfbe6daa292a64e6b6878282b6f14e2d3de
Apply patch file failed:
Repo: dpdk
24108:
patching file app/test-pmd/testpmd.c
Hunk #2 FAILED at 2239.
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-crypto
24108:
patching file app/test-pmd/testpmd.c
Hunk #2 FAILED at 2239.
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-net
24108:
patching file app/test-pmd/testpmd.c
Hunk #2 FAILED at 2239.
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-virtio
24108:
patching file app/test-pmd/testpmd.c
Hunk #2 FAILED at 2239.
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-eventdev
24108:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 971.
Hunk #2 FAILED at 2238.
2 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
DPDK STV team
reply other threads:[~2017-05-05 0:25 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='63cbe6$12mr1oj@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=pablo.de.lara.guarch@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).