From: sys_stv@intel.com
To: pablo.de.lara.guarch@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15442-15444 hash: reorganize bucket structure
Date: 02 Sep 2016 00:51:02 -0700 [thread overview]
Message-ID: <60e943$v4c7r2@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15442-15444
http://www.dpdk.org/dev/patchwork/patch/15444/
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Fri, 26 Aug 2016 22:34:45 +0100
DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
Check patch:Success
patch file error:
15442:
patching file lib/librte_hash/rte_cuckoo_hash.c Hunk #1 succeeded at 419 with fuzz 1 (offset -1 lines).
Hunk #2 succeeded at 432 (offset -1 lines).
Hunk #3 succeeded at 459 (offset -1 lines).
Hunk #4 succeeded at 542 (offset -1 lines).
Hunk #5 succeeded at 562 (offset -1 lines).
Hunk #6 FAILED at 610.
Hunk #7 succeeded at 630 (offset -1 lines).
Hunk #8 FAILED at 706.
Hunk #9 succeeded at 728 (offset -1 lines).
Hunk #10 succeeded at 783 (offset -1 lines).
Hunk #11 FAILED at 823.
Hunk #12 FAILED at 848.
Hunk #13 succeeded at 951 (offset -6 lines).
4 out of 13 hunks FAILED -- saving rejects to file lib/librte_hash/rte_cuckoo_hash.c.rej
patching file lib/librte_hash/rte_cuckoo_hash.h Hunk #1 succeeded at 149 (offset -2 lines).
Hunk #2 succeeded at 161 (offset -2 lines).
patching file lib/librte_hash/rte_cuckoo_hash_x86.h
Hunk #1 FAILED at 54.
Hunk #2 succeeded at 102 (offset 1 line).
Hunk #3 succeeded at 114 (offset 1 line).
Hunk #4 succeeded at 126 (offset 1 line).
Hunk #5 succeeded at 179 (offset 1 line).
1 out of 5 hunks FAILED -- saving rejects to file lib/librte_hash/rte_cuckoo_hash_x86.h.rej
DPDK STV team
reply other threads:[~2016-09-02 7:51 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='60e943$v4c7r2@orsmga002.jf.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).