From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: aber@semihalf.com
Subject: [dpdk-test-report] |FAILURE| pw30850 [PATCH] pktgen-dpdk: Add support for make O=OUTPUT option
Date: 25 Oct 2017 05:06:58 -0700 [thread overview]
Message-ID: <1a8a4b$141qsfd@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/30850
_apply patch file failure_
Submitter: Andriy Berestovskyy <aber@semihalf.com>
Date: Wed, 25 Oct 2017 13:17:00 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:5032b527831fe7f4b4025056cc6358838967b142
Repo:dpdk-next-crypto, Branch:master, CommitID:ecd0502907edce4deb866badf0bebc5f41dc4cd8
Repo:dpdk-next-net, Branch:master, CommitID:30c1c92e4ec1890183e4a42b644e8626811230fb
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:681459bf9cd5778ada011e6d8d681436ec5394f0
Apply patch file failed:
Repo: dpdk
30850:
patching file app/Makefile
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file app/Makefile.rej
Repo: dpdk-next-crypto
30850:
patching file app/Makefile
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file app/Makefile.rej
Repo: dpdk-next-net
30850:
patching file app/Makefile
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file app/Makefile.rej
Repo: dpdk-next-virtio
30850:
patching file app/Makefile
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file app/Makefile.rej
Repo: dpdk-next-eventdev
30850:
patching file app/Makefile
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file app/Makefile.rej
DPDK STV team
reply other threads:[~2017-10-25 12:07 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='1a8a4b$141qsfd@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=aber@semihalf.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).