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 v8 2/2] dts: port over dynamic config test suite
Date: Thu, 16 Jan 2025 00:02:25 -0500 [thread overview]
Message-ID: <CAJvnSUBGUN2oGA+OHTvZpsSYYTG1qRQLrny=gBF3-Tjz9biFWg@mail.gmail.com> (raw)
In-Reply-To: <20250115162959.12975-2-dmarx@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
On Wed, Jan 15, 2025 at 11:30 AM Dean Marx <dmarx@iol.unh.edu> wrote:
> + def disable_promisc_setup(self, testpmd: TestPmdShell, port_id: int)
> -> TestPmdShell:
> + """Sets up testpmd shell config for cases where promisc mode is
> disabled.
> +
> + Args:
> + testpmd: Testpmd session that is being configured.
> + port_id: Port number to disable promisc mode on.
> +
> + Returns:
> + TestPmdShell: interactive testpmd shell object.
>
I know we chatted about this way back, but I personally don't see the
stylistic benefit of returning the Testpmd shell, and rewriting the testpmd
instance via the return when calling disable_promisc_setup(). I think it
reads cleaner if these methods are void methods. But of course it's
functionally the same either way, so I'm being a little pedantic. There is
no need to change this now, again particularly with what Luca has suggested
we do with testpmd shell going forward.
> + """
> + testpmd.start()
> + testpmd.set_promisc(port=port_id, enable=False)
> + testpmd.set_forward_mode(SimpleForwardingModes.io)
> + return testpmd
> +
> + @func_test
> + def test_default_mode(self) -> None:
> + """Tests default configuration.
> +
> + Creates a testpmd shell, verifies that promiscuous mode is
> enabled by default,
> + and sends two packets; one matching source MAC address and one
> unknown.
> + Verifies that both are received.
> + """
> + with TestPmdShell(node=self.sut_node) as testpmd:
> + isPromisc =
> testpmd.show_port_info(0).is_promiscuous_mode_enabled
> + self.verify(isPromisc, "Promiscuous mode was not enabled by
> default.")
>
isPromisc should be is_promisc
>
> --
> 2.44.0
>
I will update the commit to change the camelcase to python variable style
and merge. Thank you for the testsuite Dean!
Reviewed-by: Patrick Robb <probb@iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2969 bytes --]
next prev parent reply other threads:[~2025-01-16 5:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 19:19 [PATCH v2 0/4] dts: initial dynamic config suite Dean Marx
2024-07-08 19:19 ` [PATCH v2 1/4] dts: add multicast set function to shell Dean Marx
2024-07-10 16:44 ` Jeremy Spewock
2024-07-08 19:19 ` [PATCH v2 2/4] dts: add toggle option to send and capture Dean Marx
2024-07-08 19:19 ` [PATCH v2 3/4] dts: dynamic config conf schema Dean Marx
2024-07-08 19:19 ` [PATCH v2 4/4] dts: dynamic config test suite Dean Marx
2024-07-08 19:30 ` [PATCH v3 1/4] dts: add multicast set function to shell Dean Marx
2024-07-08 19:30 ` [PATCH v3 2/4] dts: add toggle option to send and capture Dean Marx
2024-07-10 16:13 ` Jeremy Spewock
2024-07-08 19:30 ` [PATCH v3 3/4] dts: dynamic config conf schema Dean Marx
2024-07-10 16:45 ` Jeremy Spewock
2024-07-08 19:30 ` [PATCH v3 4/4] dts: dynamic config test suite Dean Marx
2024-07-10 16:45 ` Jeremy Spewock
2024-07-15 16:00 ` [PATCH v4 1/3] dts: add multicast set function to shell Dean Marx
2024-07-15 16:00 ` [PATCH v4 2/3] dts: dynamic config conf schema Dean Marx
2024-07-15 20:22 ` Jeremy Spewock
2024-07-15 16:00 ` [PATCH v4 3/3] dts: dynamic config test suite Dean Marx
2024-07-15 20:22 ` Jeremy Spewock
2024-07-15 20:22 ` [PATCH v4 1/3] dts: add multicast set function to shell Jeremy Spewock
2024-07-24 19:21 ` [PATCH v5 0/3] dts: refactored dynamic config test suite Dean Marx
2024-07-24 19:21 ` [PATCH v5 1/3] dts: add multicast set function to shell Dean Marx
2024-08-07 15:50 ` Luca Vizzarro
2024-07-24 19:21 ` [PATCH v5 2/3] dts: dynamic config conf schema Dean Marx
2024-07-26 19:35 ` Jeremy Spewock
2024-08-07 15:56 ` Luca Vizzarro
2024-07-24 19:21 ` [PATCH v5 3/3] dts: dynamic config test suite Dean Marx
2024-07-26 19:35 ` Jeremy Spewock
2024-08-07 19:18 ` [PATCH v6 0/2] dts: refactored " Dean Marx
2024-08-07 19:18 ` [PATCH v6 1/2] dts: add multicast set function to shell Dean Marx
2024-08-07 19:18 ` [PATCH v6 2/2] dts: dynamic config test suite Dean Marx
2024-10-10 20:17 ` [PATCH v7 0/2] dts: port over dynamic config suite Dean Marx
2024-10-10 20:17 ` [PATCH v7 1/2] dts: add multicast set funciton to shell Dean Marx
2024-10-10 20:17 ` [PATCH v7 2/2] dts: port over dynamic config test suite Dean Marx
2024-10-10 20:21 ` [PATCH v7 0/2] dts: port over dynamic config suite Dean Marx
2024-10-10 20:21 ` [PATCH v7 1/2] dts: add multicast set function to shell Dean Marx
2025-01-15 16:29 ` [PATCH v8 " Dean Marx
2025-01-15 16:29 ` [PATCH v8 2/2] dts: port over dynamic config test suite Dean Marx
2025-01-16 5:02 ` Patrick Robb [this message]
2025-01-16 5:16 ` Patrick Robb
2025-01-16 5:13 ` [PATCH v8 1/2] dts: add multicast set function to shell Patrick Robb
2025-01-16 5:15 ` Patrick Robb
2024-10-10 20:21 ` [PATCH v7 2/2] dts: port over dynamic config test suite 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='CAJvnSUBGUN2oGA+OHTvZpsSYYTG1qRQLrny=gBF3-Tjz9biFWg@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).