automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, gmuthukrishn@marvell.com
Subject: compilation|WARNING| pw(134158) sid(30268) job(PER_PATCH_BUILD10063)[v4, 3/3] test/dma: add SG copy tests
Date: 14 Nov 2023 12:01:29 -0800	[thread overview]
Message-ID: <c279bf$oseu0o@fmsmga004-auth.fm.intel.com> (raw)

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


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

_apply issues_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: 2023-11-13 12:53:49
Reply_mail: <c3eced01903a0e8fa8f24672a4bfb70dc9454d0f.1699879558.git.gmuthukrishn@marvell.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 4dc8a18f3499f3f69b1101c14e139c4d553558f2


* Repo: dpdk
test/dma: fix buffer auto free
    
    Buffer auto free test failed for more than 1 dma device as the device
    initialization for the test was been done only for the first dma
    device. This changeset fixes the same and also fixes the freeing of
    the uninitialised source buffer in error condition.
--
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: app/test/test_dmadev.c:837
error: app/test/test_dmadev.c: patch does not apply
Applying: test/dma: use unit test framework
Patch failed at 0001 test/dma: use unit test framework
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:[~2023-11-14 20:01 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='c279bf$oseu0o@fmsmga004-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gmuthukrishn@marvell.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).