From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: allain.legacy@windriver.com
Subject: [dpdk-test-report] |FAILURE| pw22926 [PATCH v4 4/6] cfgfile: use strnlen to constrain memchr search
Date: 01 Apr 2017 03:08:37 -0700 [thread overview]
Message-ID: <ffb989$20itke@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22926
_apply patch file failure_
Submitter: Allain Legacy <allain.legacy@windriver.com>
Date: Thu, 30 Mar 2017 14:54:05 -0400
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
Repo:dpdk-next-crypto, Branch:master, CommitID:3989a0933afab9d339ed9c6de258185d30bb7cb5
Repo:dpdk-next-net, Branch:master, CommitID:a962e4db963d57c1c4c48e46716fc5a63a59542f
Repo:dpdk-next-virtio, Branch:master, CommitID:26f5fd077415b94bb4aacd857d38ae25841f4fe7
Repo:dpdk, Branch:master, CommitID:ba82829fda022e14a938c3a669de0e634626e4c8
Apply patch file failed:
Repo: dpdk
22926:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.c.rej
Repo: dpdk-next-crypto
22926:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.c.rej
Repo: dpdk-next-net
22926:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.c.rej
Repo: dpdk-next-virtio
22926:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.c.rej
Repo: dpdk-next-eventdev
22926:
patching file lib/librte_cfgfile/rte_cfgfile.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cfgfile/rte_cfgfile.c.rej
DPDK STV team
reply other threads:[~2017-04-01 10:08 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$20itke@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=allain.legacy@windriver.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).