DPDK patches and discussions
 help / color / mirror / Atom feed
From: jspewock@iol.unh.edu
To: Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
	thomas@monjalon.net, lijuan.tu@intel.com,
	wathsala.vithanage@arm.com, probb@iol.unh.edu
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v1 0/2] Add DTS smoke tests
Date: Thu, 15 Jun 2023 16:10:58 -0400	[thread overview]
Message-ID: <20230615201318.13359-2-jspewock@iol.unh.edu> (raw)

From: Jeremy Spewock <jspewock@iol.unh.edu>

This series adds smoke tests for the new DTS framework which includes
various tests to ensure the environment was setup properly. The idea
behind these tests are to ensure the integrity of the environment before
starting the execution of DTS to "fail-fast" with more informative
logging. It tests things such as, meson driver-test and fast-test
suites, NICs being bound to the correct driver, and ensuring these
devices are present in testpmd.

RFCs for this patch:
* v3: https://mails.dpdk.org/archives/dev/2023-June/269859.html
* v2: https://mails.dpdk.org/archives/dev/2023-May/267915.html
* v1: https://mails.dpdk.org/archives/dev/2023-April/266580.html


Jeremy Spewock (2):
  dts: add smoke tests
  dts: added paramiko to dependencies

 dts/conf.yaml                                 |  13 ++
 dts/framework/config/__init__.py              | 114 +++++++++++--
 dts/framework/config/conf_yaml_schema.json    | 135 ++++++++++++++-
 dts/framework/dts.py                          | 101 ++++++++---
 dts/framework/exception.py                    |  12 ++
 dts/framework/remote_session/__init__.py      |  10 +-
 dts/framework/remote_session/os_session.py    |  34 +++-
 dts/framework/remote_session/posix_session.py |  30 ++++
 .../remote_session/remote/__init__.py         |  12 ++
 .../remote/interactive_remote_session.py      | 113 +++++++++++++
 .../remote/interactive_shell.py               |  98 +++++++++++
 .../remote_session/remote/testpmd_shell.py    |  58 +++++++
 dts/framework/test_result.py                  |  38 ++++-
 dts/framework/test_suite.py                   |  31 +++-
 dts/framework/testbed_model/node.py           |   2 +
 dts/framework/testbed_model/sut_node.py       | 110 +++++++++++-
 dts/poetry.lock                               | 160 ++++++++++++++----
 dts/pyproject.toml                            |   1 +
 dts/tests/TestSuite_smoke_tests.py            | 101 +++++++++++
 19 files changed, 1086 insertions(+), 87 deletions(-)
 create mode 100644 dts/framework/remote_session/remote/interactive_remote_session.py
 create mode 100644 dts/framework/remote_session/remote/interactive_shell.py
 create mode 100644 dts/framework/remote_session/remote/testpmd_shell.py
 create mode 100644 dts/tests/TestSuite_smoke_tests.py

-- 
2.41.0


             reply	other threads:[~2023-06-15 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 20:10 jspewock [this message]
2023-06-15 20:10 ` [PATCH v1 1/2] dts: add " jspewock
2023-07-06 14:53   ` Juraj Linkeš
2023-07-07 23:06     ` Jeremy Spewock
2023-07-11  8:16       ` Juraj Linkeš
2023-07-11 18:09         ` Jeremy Spewock
2023-07-12  6:30           ` Juraj Linkeš
2023-07-12 13:46             ` Jeremy Spewock
2023-06-15 20:11 ` [PATCH v1 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=20230615201318.13359-2-jspewock@iol.unh.edu \
    --to=jspewock@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@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).