From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86090) [v2, 6/6] doc: new net PMD iavf_be
Date: 06 Jan 2021 23:38:41 -0800 [thread overview]
Message-ID: <93cfb9$gvt198@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86090
_apply issues_
Submitter: Jingjing Wu <jingjing.wu@intel.com>
Date: 2021-01-07 07:15:03
Reply_mail: 20210107071503.14720-7-jingjing.wu@intel.com
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 0f83e2244608e93b66602e0753c1a22a0e98143e
Repo:dpdk, CommitID: b031e13d7f0dc7cba9bc5befe968b67832021a59
* Repo: dpdk-next-net-intel
Applying: doc: new net PMD iavf_be
error: sha1 information is lacking or useless (MAINTAINERS).
error: could not build fake ancestor
Patch failed at 0006 doc: new net PMD iavf_be
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
build: fix plugin load on static build
When dpdk is compiled as static libraries, it is not possible
to load a plugin from an application. We get the following error:
EAL: librte_pmd_xxxx.so: undefined symbol: per_lcore__rte_errno
--
Applying: doc: new net PMD iavf_be
error: sha1 information is lacking or useless (MAINTAINERS).
error: could not build fake ancestor
Patch failed at 0006 doc: new net PMD iavf_be
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-01-07 7:38 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='93cfb9$gvt198@fmsmga005-auth.fm.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).