From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: santosh.shukla@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw24238 [PATCH 2/2] test/test_mbuf: Free mempool on exit
Date: 11 May 2017 08:55:59 -0700 [thread overview]
Message-ID: <63cbe6$12pono1@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24238
_apply patch file failure_
Submitter: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Date: Thu, 11 May 2017 16:00:44 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:222555480a7f9979d10faa9bb8b9773b0e1aa058
Repo:dpdk-next-net, Branch:master, CommitID:222555480a7f9979d10faa9bb8b9773b0e1aa058
Repo:dpdk-next-virtio, Branch:master, CommitID:ad06857e40c3d30f92ede00e840bbd8e6a69b703
Repo:dpdk, Branch:master, CommitID:222555480a7f9979d10faa9bb8b9773b0e1aa058
Apply patch file failed:
Repo: dpdk
24238:
patching file test/test/test_mbuf.c
Hunk #1 FAILED at 784.
Hunk #2 succeeded at 813 with fuzz 1 (offset 1 line).
Hunk #4 FAILED at 1061.
Hunk #5 succeeded at 1069 (offset -4 lines).
Hunk #6 FAILED at 1083.
Hunk #7 FAILED at 1117.
4 out of 7 hunks FAILED -- saving rejects to file test/test/test_mbuf.c.rej
Repo: dpdk-next-crypto
24238:
patching file test/test/test_mbuf.c
Hunk #1 FAILED at 784.
Hunk #2 succeeded at 813 with fuzz 1 (offset 1 line).
Hunk #4 FAILED at 1061.
Hunk #5 succeeded at 1069 (offset -4 lines).
Hunk #6 FAILED at 1083.
Hunk #7 FAILED at 1117.
4 out of 7 hunks FAILED -- saving rejects to file test/test/test_mbuf.c.rej
Repo: dpdk-next-net
24238:
patching file test/test/test_mbuf.c
Hunk #1 FAILED at 784.
Hunk #2 succeeded at 813 with fuzz 1 (offset 1 line).
Hunk #4 FAILED at 1061.
Hunk #5 succeeded at 1069 (offset -4 lines).
Hunk #6 FAILED at 1083.
Hunk #7 FAILED at 1117.
4 out of 7 hunks FAILED -- saving rejects to file test/test/test_mbuf.c.rej
Repo: dpdk-next-virtio
24238:
patching file test/test/test_mbuf.c
Hunk #1 FAILED at 784.
Hunk #2 succeeded at 813 with fuzz 1 (offset 1 line).
Hunk #4 FAILED at 1061.
Hunk #5 succeeded at 1069 (offset -4 lines).
Hunk #6 FAILED at 1083.
Hunk #7 FAILED at 1117.
4 out of 7 hunks FAILED -- saving rejects to file test/test/test_mbuf.c.rej
Repo: dpdk-next-eventdev
24238:
patching file test/test/test_mbuf.c
Hunk #1 FAILED at 784.
Hunk #2 succeeded at 813 with fuzz 1 (offset 1 line).
Hunk #4 FAILED at 1061.
Hunk #5 succeeded at 1069 (offset -4 lines).
Hunk #6 FAILED at 1083.
Hunk #7 FAILED at 1117.
4 out of 7 hunks FAILED -- saving rejects to file test/test/test_mbuf.c.rej
DPDK STV team
reply other threads:[~2017-05-11 15:56 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='63cbe6$12pono1@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=santosh.shukla@caviumnetworks.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).