From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-test-report] |FAILURE| pw27420 [PATCH] doc: move metrics libs to device API section
Date: 03 Aug 2017 11:25:23 -0700 [thread overview]
Message-ID: <ffb989$3hrits@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27420
_apply patch file failure_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thu, 3 Aug 2017 17:56:05 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:cb78ef9859ff68b9e260a844f151055ebd9ae78f
Repo:dpdk-next-crypto, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Repo:dpdk-next-net, Branch:master, CommitID:c9f814f331658844c7bc07879daa268f5e54bb5a
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:c9f814f331658844c7bc07879daa268f5e54bb5a
Apply patch file failed:
Repo: dpdk
27420:
patching file doc/api/doxy-api-index.md
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file doc/api/doxy-api-index.md.rej
Repo: dpdk-next-crypto
27420:
patching file doc/api/doxy-api-index.md
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file doc/api/doxy-api-index.md.rej
Repo: dpdk-next-net
27420:
patching file doc/api/doxy-api-index.md
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file doc/api/doxy-api-index.md.rej
Repo: dpdk-next-virtio
27420:
patching file doc/api/doxy-api-index.md
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file doc/api/doxy-api-index.md.rej
Repo: dpdk-next-eventdev
27420:
patching file doc/api/doxy-api-index.md
Hunk #1 succeeded at 44 (offset 1 line).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file doc/api/doxy-api-index.md.rej
DPDK STV team
reply other threads:[~2017-08-03 18: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='ffb989$3hrits@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).