automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, fengchengwen@huawei.com
Subject: [dpdk-test-report] |WARNING| pw(116809) sid(24808) job(PER_PATCH_BUILD4319)[v3, 10/10] test/memarea: support no MT-safe test
Date: 24 Sep 2022 01:08:33 -0700	[thread overview]
Message-ID: <e7de8f$s9a49q@fmsmga005-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/116809

_apply issues_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: 2022-09-24 07:49:51
Reply_mail: <20220924074951.31814-11-fengchengwen@huawei.com>

DPDK git baseline:
	Repo:dpdk, CommitID: fa7723b5e32f0eb8c513a5c51ab131a7bf159446


* Repo: dpdk
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: lib/memarea/rte_memarea.c:2
error: lib/memarea/rte_memarea.c: patch does not apply
error: patch failed: lib/memarea/rte_memarea.h:194
error: lib/memarea/rte_memarea.h: patch does not apply
error: patch failed: lib/memarea/version.map:4
error: lib/memarea/version.map: patch does not apply
Applying: memarea: introduce memarea library
Applying: test/memarea: support memarea test
Applying: memarea: support dump API
Patch failed at 0003 memarea: support dump API
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:[~2022-09-24  8:08 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='e7de8f$s9a49q@fmsmga005-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=fengchengwen@huawei.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).