From: jspewock@iol.unh.edu
To: dev@dpdk.org
Cc: Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [RFC v2 0/2] add DTS smoke tests
Date: Fri, 12 May 2023 15:25:40 -0400 [thread overview]
Message-ID: <20230512192540.401-2-jspewock@iol.unh.edu> (raw)
From: Jeremy Spewock <jspewock@iol.unh.edu>
This update to the RFC adds a few more things such as physical devices
and virtual devices to the config, driver checks in the smoke tests, and interactive shell
handling.
Interactive shells are handled by creating two SSH connections upon
connecting to the SUT, one which is for normal non-interactive
opertaions and another (using paramiko) that is reserved for interactive shells. This
interactive session is stored in the main session of the SUT and can be
piloted using the interactive handler. This handler creates a new
channel off the session and provides methods for sending commands both
blindly and by expecting output. Then, classes are made for individual
DPDK applications that use one of these interactive handlers and know
how to handle that applications specific behaviors and outputs.
Old RFC:
* http://patches.dpdk.org/project/dpdk/patch/20230413175415.7683-3-jspewock@iol.unh.edu/
Jeremy Spewock (1):
dts: added paramiko to dependencies
Jeremy Spewock (1):
dts: add smoke tests
dts/conf.yaml | 9 +
dts/framework/config/__init__.py | 21 +++
dts/framework/config/conf_yaml_schema.json | 32 +++-
dts/framework/dts.py | 19 ++-
dts/framework/exception.py | 11 ++
dts/framework/remote_session/os_session.py | 6 +-
.../remote_session/remote/__init__.py | 28 +++
dts/framework/test_result.py | 13 +-
dts/framework/test_suite.py | 24 ++-
dts/framework/testbed_model/__init__.py | 5 +
.../interactive_apps/__init__.py | 6 +
.../interactive_apps/interactive_command.py | 57 +++++++
.../interactive_apps/testpmd_driver.py | 24 +++
dts/framework/testbed_model/node.py | 2 +
dts/framework/testbed_model/sut_node.py | 6 +
dts/poetry.lock | 160 ++++++++++++++----
dts/pyproject.toml | 1 +
dts/tests/TestSuite_smoke_tests.py | 94 ++++++++++
18 files changed, 472 insertions(+), 46 deletions(-)
create mode 100644 dts/framework/testbed_model/interactive_apps/__init__.py
create mode 100644 dts/framework/testbed_model/interactive_apps/interactive_command.py
create mode 100644 dts/framework/testbed_model/interactive_apps/testpmd_driver.py
create mode 100644 dts/tests/TestSuite_smoke_tests.py
--
2.40.1
next reply other threads:[~2023-05-12 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 19:25 jspewock [this message]
2023-05-12 19:25 ` [RFC v2 1/2] dts: add " jspewock
2023-05-23 8:05 ` Juraj Linkeš
2023-05-23 8:33 ` Juraj Linkeš
2023-05-24 20:44 ` Jeremy Spewock
2023-05-25 8:33 ` Juraj Linkeš
2023-05-25 18:02 ` Jeremy Spewock
2023-05-26 7:36 ` Juraj Linkeš
2023-05-26 13:24 ` Jeremy Spewock
2023-05-24 10:03 ` Juraj Linkeš
2023-05-25 15:40 ` Jeremy Spewock
2023-05-12 19:25 ` [RFC v2 2/2] dts: added paramiko to dependencies jspewock
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=20230512192540.401-2-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=dev@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).