From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25848[dpdk-dev] lib/lib_eal:fix the pointer 'elem' may be NULL bug
Date: 21 May 2018 19:33:43 -0700 [thread overview]
Message-ID: <0590c7$1n7eg5@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25848
_apply issues_
Submitter: Xie RongQiang <xie.rongqiang@zte.com.cn>
Date: 2017-06-28 08:12:35
DPDK git baseline:
Repo:dpdk-master, CommitID: fe613657ce486083a3ed96890c95de4f35c8593b
Repo:dpdk-next-eventdev, CommitID: 3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-net, CommitID: db1a11e519444772a18f50bef5ded66e1d43cae2
Repo:dpdk-next-crypto, CommitID: a7ac03988bb2c64ad9c58970f0b9fd582e791058
Repo:dpdk-next-virtio, CommitID: 317fe244a65ea2a5753e839f7d094b3d8677fac6
*Repo: dpdk-master
/root/regression_share/patches/25848.patch:31: trailing whitespace.
Checking patch lib/librte_eal/common/eal_common_memzone.c...
error: while searching for:
}
const struct malloc_elem *elem = malloc_elem_from_data(mz_addr);
/* fill the zone in config */
mz = get_next_free_memzone();
error: patch failed: lib/librte_eal/common/eal_common_memzone.c:238
error: lib/librte_eal/common/eal_common_memzone.c: patch does not apply
*Repo: dpdk-next-eventdev
/root/regression_share/patches/25848.patch:31: trailing whitespace.
Checking patch lib/librte_eal/common/eal_common_memzone.c...
error: while searching for:
}
const struct malloc_elem *elem = malloc_elem_from_data(mz_addr);
/* fill the zone in config */
mz = get_next_free_memzone();
error: patch failed: lib/librte_eal/common/eal_common_memzone.c:238
error: lib/librte_eal/common/eal_common_memzone.c: patch does not apply
*Repo: dpdk-next-net
/root/regression_share/patches/25848.patch:31: trailing whitespace.
Checking patch lib/librte_eal/common/eal_common_memzone.c...
error: while searching for:
}
const struct malloc_elem *elem = malloc_elem_from_data(mz_addr);
/* fill the zone in config */
mz = get_next_free_memzone();
error: patch failed: lib/librte_eal/common/eal_common_memzone.c:238
error: lib/librte_eal/common/eal_common_memzone.c: patch does not apply
*Repo: dpdk-next-crypto
/root/regression_share/patches/25848.patch:31: trailing whitespace.
Checking patch lib/librte_eal/common/eal_common_memzone.c...
error: while searching for:
}
const struct malloc_elem *elem = malloc_elem_from_data(mz_addr);
/* fill the zone in config */
mz = get_next_free_memzone();
error: patch failed: lib/librte_eal/common/eal_common_memzone.c:238
error: lib/librte_eal/common/eal_common_memzone.c: patch does not apply
*Repo: dpdk-next-virtio
/root/regression_share/patches/25848.patch:31: trailing whitespace.
Checking patch lib/librte_eal/common/eal_common_memzone.c...
error: while searching for:
}
const struct malloc_elem *elem = malloc_elem_from_data(mz_addr);
/* fill the zone in config */
mz = get_next_free_memzone();
error: patch failed: lib/librte_eal/common/eal_common_memzone.c:238
error: lib/librte_eal/common/eal_common_memzone.c: patch does not apply
DPDK STV team
reply other threads:[~2018-05-22 2:33 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='0590c7$1n7eg5@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@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).