automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, jspewock@iol.unh.edu
Subject: compilation|WARNING| pw(141129) sid(32159) job(PER_PATCH_BUILD12247)[v4, 4/4] dts: add test case that utilizes offload to pmd_buffer_scatter
Date: 13 Jun 2024 11:22:40 -0700	[thread overview]
Message-ID: <09f2c0$16fmd1@fmviesa009-auth.fm.intel.com> (raw)

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


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

_apply issues_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: 2024-06-13 18:15:10
Reply_mail: <20240613181510.30135-5-jspewock@iol.unh.edu>

DPDK git baseline:
	Repo:dpdk, CommitID: 6484c847d4e48386904841d6b7062007f837dfb4


* 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: dts/framework/remote_session/__init__.py:21
error: dts/framework/remote_session/__init__.py: patch does not apply
error: patch failed: dts/framework/remote_session/testpmd_shell.py:227
error: dts/framework/remote_session/testpmd_shell.py: patch does not apply
error: patch failed: dts/framework/testbed_model/sut_node.py:243
error: dts/framework/testbed_model/sut_node.py: patch does not apply
Applying: dts: add context manager for interactive shells
Patch failed at 0001 dts: add context manager for interactive shells
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:[~2024-06-13 18:22 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='09f2c0$16fmd1@fmviesa009-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=jspewock@iol.unh.edu \
    --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).