DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Dean Marx <dmarx@iol.unh.edu>
Cc: npratte@iol.unh.edu, luca.vizzarro@arm.com,
	yoan.picchi@foss.arm.com,  Honnappa.Nagarahalli@arm.com,
	paul.szczepanek@arm.com, dev@dpdk.org
Subject: Re: [PATCH v2] dts: add SUT cleanup to framework
Date: Sun, 9 Feb 2025 16:26:42 -0500	[thread overview]
Message-ID: <CAJvnSUDic-6rBrPC-YPT3C7J-xVXjAwSGJah-gavNfPaqoTgRw@mail.gmail.com> (raw)
In-Reply-To: <20250130221324.75711-1-dmarx@iol.unh.edu>

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

On Thu, Jan 30, 2025 at 5:13 PM Dean Marx <dmarx@iol.unh.edu> wrote:

> Add method cleanup_sut to framework that removes a
> DPDK source from a SUT node at the conclusion of a testrun.
> This will only run when the DPDK source is being copied
> from the DTS engine node during the testrun
> (when remote=false in the conf.yaml).
>
> Signed-off-by: Dean Marx <dmarx@iol.unh.edu>
> ---
>  dts/framework/runner.py                 |  2 +-
>  dts/framework/testbed_model/sut_node.py | 21 ++++++++++++++++++---
>  2 files changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/dts/framework/runner.py b/dts/framework/runner.py
> index 9f9789cf49..367034e038 100644
> --- a/dts/framework/runner.py
> +++ b/dts/framework/runner.py
> @@ -336,7 +336,7 @@ def _run_test_run(
>          finally:
>              try:
>                  self._logger.set_stage(DtsStage.test_run_teardown)
> -                sut_node.tear_down_test_run()
> +
> sut_node.tear_down_test_run(test_run_config.dpdk_config.dpdk_location)
>                  tg_node.tear_down_test_run()
>                  test_run_result.update_teardown(Result.PASS)
>              except Exception as e:
> diff --git a/dts/framework/testbed_model/sut_node.py
> b/dts/framework/testbed_model/sut_node.py
> index 483733cede..c73500b146 100644
> --- a/dts/framework/testbed_model/sut_node.py
> +++ b/dts/framework/testbed_model/sut_node.py
> @@ -188,6 +188,19 @@ def path_to_devbind_script(self) -> PurePath | str:
>              )
>          return self._path_to_devbind_script
>
> +    def cleanup_sut(self, dpdk_build_location, remote_tree: str |
> PurePath | None) -> None:
>

I think you have a missing type hint here for the dpdk_build_location arg.
I think it is a LocalDPDKLocation.


> --
> 2.48.1
>
>
While you're at it, you can edit the commit message to replace the
reference to conf.yaml (no longer named this) to the new name or just
"configuration."

Thanks and sorry I missed this on the first look through! Can merge this
asap once you make the edits.

[-- Attachment #2: Type: text/html, Size: 2867 bytes --]

      reply	other threads:[~2025-02-09 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 20:59 [RFC PATCH 0/1] " Dean Marx
2024-12-09 20:59 ` [RFC PATCH 1/1] " Dean Marx
2025-01-30  5:31   ` Patrick Robb
2025-01-30  6:30     ` Patrick Robb
2025-01-30 21:32     ` Dean Marx
2025-01-30 22:13   ` [PATCH v2] " Dean Marx
2025-02-09 21:26     ` Patrick Robb [this message]

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=CAJvnSUDic-6rBrPC-YPT3C7J-xVXjAwSGJah-gavNfPaqoTgRw@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=luca.vizzarro@arm.com \
    --cc=npratte@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    --cc=yoan.picchi@foss.arm.com \
    /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).