From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: baruch@tkos.co.il
Subject: [dpdk-test-report] |FAILURE| pw17707 [PATCH, v2, 3/3] doc: consistently quote directory names
Date: 06 Dec 2016 17:24:09 -0800 [thread overview]
Message-ID: <587443$duecf@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Test-Label: Intel Per-patch compilation check
Test-Status: FAILURE
Patchwork ID: 17707
http://www.dpdk.org/dev/patchwork/patch/17707
Submitter: Baruch Siach <baruch@tkos.co.il>
Date: Tue, 6 Dec 2016 14:38:10 +0200
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:e6c7b6ec57f3527ce55fa3e0d2a8ed1533722253
Repo:dpdk-next-net, Branch:master, CommitID:e62535ca8e47819e1ccaa64bf8f91498ce568051
Repo:dpdk-next-virtio, Branch:master, CommitID:b5415fbc69dd33a1bb64a140b2f6bc73d11e4d22
Repo:dpdk, Branch:master, CommitID:8ee94d8aee73d39f50dea753da787c285f228b5c
Apply patch file failed:
Repo: dpdk-next-crypto
17707:
patching file doc/guides/prog_guide/source_org.rst
Hunk #1 FAILED at 125.
Hunk #2 succeeded at 136 (offset 1 line).
Hunk #3 FAILED at 162.
2 out of 3 hunks FAILED -- saving rejects to file doc/guides/prog_guide/source_org.rst.rej
Repo: dpdk-next-net
17707:
patching file doc/guides/prog_guide/source_org.rst
Hunk #1 FAILED at 125.
Hunk #2 succeeded at 136 (offset 1 line).
Hunk #3 FAILED at 162.
2 out of 3 hunks FAILED -- saving rejects to file doc/guides/prog_guide/source_org.rst.rej
Repo: dpdk-next-virtio
17707:
patching file doc/guides/prog_guide/source_org.rst
Hunk #1 FAILED at 125.
Hunk #2 succeeded at 136 (offset 1 line).
Hunk #3 FAILED at 162.
2 out of 3 hunks FAILED -- saving rejects to file doc/guides/prog_guide/source_org.rst.rej
Repo: dpdk
17707:
patching file doc/guides/prog_guide/source_org.rst
Hunk #1 FAILED at 125.
Hunk #2 succeeded at 136 (offset 1 line).
Hunk #3 FAILED at 162.
2 out of 3 hunks FAILED -- saving rejects to file doc/guides/prog_guide/source_org.rst.rej
DPDK STV team
reply other threads:[~2016-12-07 1:24 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='587443$duecf@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=baruch@tkos.co.il \
--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).