From: Nicholas Pratte <npratte@iol.unh.edu>
To: yoan.picchi@foss.arm.com, thomas@monjalon.net,
luca.vizzarro@arm.com, probb@iol.unh.edu,
Honnappa.Nagarahalli@arm.com, stephen@networkplumber.org,
paul.szczepanek@arm.com, dmarx@iol.unh.edu, thomas.wilks@arm.com,
ian.stokes@intel.com
Cc: dev@dpdk.org, Nicholas Pratte <npratte@iol.unh.edu>
Subject: [PATCH 0/2] remove 'requires_forwarding_restart' from framework
Date: Fri, 31 Jan 2025 14:38:01 -0500 [thread overview]
Message-ID: <20250131193803.168498-1-npratte@iol.unh.edu> (raw)
While I initially thought that this would improve the cleanliness of
future test suite writing, because of the various nuances of each
testpmd run-time command, having the framework managing forwarding when
needed introduces far too many additional challenges, such that, it
simply is not worth the time implementing this.
Arguably, it also makes sense to have these mechanics (such as
forwarding restarts) written explicitly within the test suites.
Thank you Luca for pointing out this issue and its potential
side-effects.
Nicholas Pratte (2):
dts: remove 'requires_forwarding_restart' from framework
dts: rework run-time MTU adjustment test case
dts/framework/remote_session/testpmd_shell.py | 26 +------------------
dts/tests/TestSuite_mtu.py | 8 +++++-
2 files changed, 8 insertions(+), 26 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-31 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:38 Nicholas Pratte [this message]
2025-01-31 19:38 ` [PATCH 1/2] dts: " Nicholas Pratte
2025-01-31 21:00 ` Luca Vizzarro
2025-01-31 19:38 ` [PATCH 2/2] dts: rework run-time MTU adjustment test case Nicholas Pratte
2025-01-31 21:08 ` Luca Vizzarro
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=20250131193803.168498-1-npratte@iol.unh.edu \
--to=npratte@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=ian.stokes@intel.com \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.org \
--cc=thomas.wilks@arm.com \
--cc=thomas@monjalon.net \
--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).