From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw69953[v3, 6/7] bus/pci: introduce Windows support with stubs
Date: 07 May 2020 16:33:51 -0700 [thread overview]
Message-ID: <fecc85$a3p9c2@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/69953
_apply issues_
Submitter: Tal Shnaiderman <talshn@mellanox.com>
Date: 2020-05-07 12:16:45
Reply_mail: 20200507121646.624-7-talshn@mellanox.com
DPDK git baseline:
Repo:dpdk, CommitID: dec44d41109dac609d83805c0b906df446f8680e
*Repo: dpdk
'eal_common_class.c',
'eal_common_devargs.c',
'eal_common_errno.c',
'eal_common_fbarray.c',
error: patch failed: lib/librte_eal/common/meson.build:7
error: lib/librte_eal/common/meson.build: patch does not apply
Checking patch lib/librte_eal/rte_eal_exports.def...
error: while searching for:
__rte_panic
rte_calloc
rte_calloc_socket
rte_eal_get_configuration
rte_eal_has_hugepages
rte_eal_init
error: patch failed: lib/librte_eal/rte_eal_exports.def:2
error: lib/librte_eal/rte_eal_exports.def: patch does not apply
Checking patch lib/librte_eal/windows/eal.c...
Hunk #1 succeeded at 225 (offset -68 lines).
Hunk #2 succeeded at 246 (offset -122 lines).
Hunk #3 succeeded at 281 (offset -122 lines).
DPDK STV team
reply other threads:[~2020-05-07 23: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='fecc85$a3p9c2@orsmga001.jf.intel.com' \
--to=sys_stv@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).