From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: tiwei.bie@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25043 [PATCH v3 2/2] contigmem: don't zero the pages during each mmap
Date: 04 Jun 2017 01:28:17 -0700 [thread overview]
Message-ID: <ffb989$2qta7p@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2948 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25043
_apply patch file failure_
Submitter: Tiwei Bie <tiwei.bie@intel.com>
Date: Sun, 4 Jun 2017 13:53:24 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7021fcbb2f5a4fc3e32f2bfd1a27f3dc671d3476
Repo:dpdk-next-crypto, Branch:master, CommitID:bc6ebd8c3e7391d3d0d909a9a068caf0f2171103
Repo:dpdk-next-net, Branch:master, CommitID:9b0a01bdd2ff38efc7cd83d65e7e071aebe712f5
Repo:dpdk-next-virtio, Branch:master, CommitID:1ee9702c260bbd4a282efdeaa7277ddbfc87177a
Repo:dpdk, Branch:master, CommitID:9d9949d67ca84501156bd26501bb168900f1c6e4
Apply patch file failed:
Repo: dpdk
25043:
patching file lib/librte_eal/bsdapp/contigmem/contigmem.c
Hunk #4 FAILED at 140.
Hunk #5 FAILED at 157.
Hunk #6 FAILED at 186.
Hunk #7 succeeded at 188 (offset -11 lines).
Hunk #8 succeeded at 214 (offset -11 lines).
Hunk #9 succeeded at 222 (offset -11 lines).
Hunk #10 succeeded at 348 (offset -11 lines).
3 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/contigmem/contigmem.c.rej
Repo: dpdk-next-crypto
25043:
patching file lib/librte_eal/bsdapp/contigmem/contigmem.c
Hunk #4 FAILED at 140.
Hunk #5 FAILED at 157.
Hunk #6 FAILED at 186.
Hunk #7 succeeded at 188 (offset -11 lines).
Hunk #8 succeeded at 214 (offset -11 lines).
Hunk #9 succeeded at 222 (offset -11 lines).
Hunk #10 succeeded at 348 (offset -11 lines).
3 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/contigmem/contigmem.c.rej
Repo: dpdk-next-net
25043:
patching file lib/librte_eal/bsdapp/contigmem/contigmem.c
Hunk #4 FAILED at 140.
Hunk #5 FAILED at 157.
Hunk #6 FAILED at 186.
Hunk #7 succeeded at 188 (offset -11 lines).
Hunk #8 succeeded at 214 (offset -11 lines).
Hunk #9 succeeded at 222 (offset -11 lines).
Hunk #10 succeeded at 348 (offset -11 lines).
3 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/contigmem/contigmem.c.rej
Repo: dpdk-next-virtio
25043:
patching file lib/librte_eal/bsdapp/contigmem/contigmem.c
Hunk #4 FAILED at 140.
Hunk #5 FAILED at 157.
Hunk #6 FAILED at 186.
Hunk #7 succeeded at 188 (offset -11 lines).
Hunk #8 succeeded at 214 (offset -11 lines).
Hunk #9 succeeded at 222 (offset -11 lines).
Hunk #10 succeeded at 348 (offset -11 lines).
3 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/contigmem/contigmem.c.rej
Repo: dpdk-next-eventdev
25043:
patching file lib/librte_eal/bsdapp/contigmem/contigmem.c
Hunk #4 FAILED at 140.
Hunk #5 FAILED at 157.
Hunk #6 FAILED at 186.
Hunk #7 succeeded at 188 (offset -11 lines).
Hunk #8 succeeded at 214 (offset -11 lines).
Hunk #9 succeeded at 222 (offset -11 lines).
Hunk #10 succeeded at 348 (offset -11 lines).
3 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/contigmem/contigmem.c.rej
DPDK STV team
reply other threads:[~2017-06-04 8:28 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$2qta7p@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=tiwei.bie@intel.com \
/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).