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

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

Addresses comments on previous patch and polishes code from that
version. Also adds documentation to the InteractiveApp class.

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

Previous patch:
* v1: https://mails.dpdk.org/archives/dev/2023-June/271309.html
* v2: https://mails.dpdk.org/archives/dev/2023-July/272833.html
* v3: https://mails.dpdk.org/archives/dev/2023-July/272930.html
* v4: https://mails.dpdk.org/archives/dev/2023-July/272964.html
* v5: https://mails.dpdk.org/archives/dev/2023-July/272983.html
* v6: https://mails.dpdk.org/archives/dev/2023-July/273019.html
* v7: https://mails.dpdk.org/archives/dev/2023-July/273028.html
* v8: https://mails.dpdk.org/archives/dev/2023-July/273117.html

Jeremy Spewock (1):
  dts: add smoke tests

 dts/conf.yaml                                 |  17 +-
 dts/framework/config/__init__.py              |  79 ++++++--
 dts/framework/config/conf_yaml_schema.json    | 142 ++++++++++++++-
 dts/framework/dts.py                          |  84 ++++++---
 dts/framework/exception.py                    |  12 ++
 dts/framework/remote_session/__init__.py      |  13 +-
 dts/framework/remote_session/linux_session.py |   3 +-
 dts/framework/remote_session/os_session.py    |  49 ++++-
 dts/framework/remote_session/posix_session.py |  29 ++-
 .../remote_session/remote/__init__.py         |  10 ++
 .../remote/interactive_remote_session.py      |  82 +++++++++
 .../remote/interactive_shell.py               | 131 ++++++++++++++
 .../remote_session/remote/testpmd_shell.py    |  49 +++++
 dts/framework/test_result.py                  |  24 ++-
 dts/framework/test_suite.py                   |  10 +-
 dts/framework/testbed_model/node.py           |  43 ++++-
 dts/framework/testbed_model/sut_node.py       | 169 +++++++++++++-----
 dts/framework/utils.py                        |   3 +
 dts/tests/TestSuite_smoke_tests.py            | 114 ++++++++++++
 19 files changed, 969 insertions(+), 94 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-07-18 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 14:44 jspewock [this message]
2023-07-18 14:44 ` [PATCH v9 1/1] dts: add " 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=20230718144659.14328-3-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).