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: [RFC PATCH 1/1] dts: add SUT cleanup to framework
Date: Thu, 30 Jan 2025 00:31:36 -0500	[thread overview]
Message-ID: <CAJvnSUA8w0-JyPnUuX8DwAXi0wYjFkhO7h+2M2CvnmzbMzBhUQ@mail.gmail.com> (raw)
In-Reply-To: <20241209205902.18321-2-dmarx@iol.unh.edu>

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

On Mon, Dec 9, 2024 at 2:58 PM Dean Marx <dmarx@iol.unh.edu> wrote:

>
> -                sut_node.tear_down_test_run()
> +                sut_node.tear_down_test_run(test_run_config.dpdk_config)
>

My first question was why is there a need to pass all of dpdk_config
through from here all the way to cleanup_sut()? Is it sufficient to extract
dpdk_location from dpdk_config at the beginning here, and pass along just
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 14d77c50a6..d39c1bd632 100644
> --- a/dts/framework/testbed_model/sut_node.py
> +++ b/dts/framework/testbed_model/sut_node.py
> @@ -175,6 +175,21 @@ def path_to_devbind_script(self) -> PurePath | str:
>              )
>          return self._path_to_devbind_script
>
> +    def cleanup_sut(
> +        self, dpdk_build_config: DPDKBuildConfiguration, remote_tree: str
> | PurePath | None
>

I understand the need for str or PurePath, but can you explain why None is
included in the union?


> --
> 2.44.0
>
>
There was also discussion at the previous DTS meeting about appending the
datetime to the dpdk artifacts when they're copied over to the SUT (a way
to create artifact uniqueness). It's not really within the scope of this
patchseries, but it wouldn't hurt for us to touch base - maybe you can do
this next.

Looks good to me overall. Once you submit the v2 I will leave a little time
for other comments, otherwise I will merge.

Thanks Dean.

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

  reply	other threads:[~2025-01-30  5:34 UTC|newest]

Thread overview: 6+ 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 [this message]
2025-01-30  6:30     ` Patrick Robb
2025-01-30 21:32     ` Dean Marx
2025-01-30 22:13   ` [PATCH v2] " Dean Marx

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=CAJvnSUA8w0-JyPnUuX8DwAXi0wYjFkhO7h+2M2CvnmzbMzBhUQ@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).