From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw135212 [PATCH] [v4, 2/7] dts: allow passing parameters into interactive apps
Date: Thu, 14 Dec 2023 19:22:38 -0800 (PST) [thread overview]
Message-ID: <657bc67e.0d0a0220.ba5a8.55c6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/135212
_apply patch failure_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thursday, December 14 2023 22:10:08
Applied on: CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
Apply patch set 135212 failed:
Checking patch dts/framework/remote_session/remote/testpmd_shell.py...
error: while searching for:
def _start_application(self, get_privileged_command: Callable[[str], str] | None) -> None:
"""See "_start_application" in InteractiveShell."""
self._app_args += " -- -i"
super()._start_application(get_privileged_command)
def start(self, verify: bool = True) -> None:
error: patch failed: dts/framework/remote_session/remote/testpmd_shell.py:62
Checking patch dts/framework/testbed_model/sut_node.py...
Applying patch dts/framework/remote_session/remote/testpmd_shell.py with 1 reject...
Rejected hunk #1.
Applied patch dts/framework/testbed_model/sut_node.py cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/dts/framework/remote_session/remote/testpmd_shell.py b/dts/framework/remote_session/remote/testpmd_shell.py (rejected hunks)
@@ -62,7 +62,7 @@ class TestPmdShell(InteractiveShell):
def _start_application(self, get_privileged_command: Callable[[str], str] | None) -> None:
"""See "_start_application" in InteractiveShell."""
- self._app_args += " -- -i"
+ self._app_args += " -i"
super()._start_application(get_privileged_command)
def start(self, verify: bool = True) -> None:
https://lab.dpdk.org/results/dashboard/patchsets/28634/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-12-15 3: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=657bc67e.0d0a0220.ba5a8.55c6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@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).