From: Jakub Kicinski <kuba@kernel•org>
To: Michal Michalik <michal.michalik@intel•com>
Cc: netdev@vger•kernel.org, vadim.fedorenko@linux•dev,
jiri@resnulli•us, arkadiusz.kubalewski@intel•com,
jonathan.lemon@gmail•com, pabeni@redhat•com, poros@redhat•com,
milena.olech@intel•com, mschmidt@redhat•com,
linux-clk@vger•kernel.org, bvanassche@acm•org
Subject: Re: [PATCH RFC net-next v1 2/2] selftests/dpll: add DPLL system integration selftests
Date: Fri, 18 Aug 2023 14:08:02 -0700 [thread overview]
Message-ID: <20230818140802.063aae1f@kernel.org> (raw)
In-Reply-To: <20230817152209.23868-3-michal.michalik@intel.com>
On Thu, 17 Aug 2023 17:22:09 +0200 Michal Michalik wrote:
> High level flow of DPLL subsystem integration selftests:
> (after running run_dpll_tests.sh or 'make -C tools/testing/selftests')
> 1) check if Python in correct version is installed,
> 2) create temporary Python virtual environment,
> 3) install all the required libraries,
> 4) run the tests,
> 5) do cleanup.
How fragile do you reckon this setup will be?
I mean will it work reliably across distros and various VM setups?
I have tried writing tests based on ynl.py and the C codegen, and
I can't decide whether the python stuff is easy enough to deploy.
Much easier to scp over to the test host a binary based on the
C code. But typing tests in python is generally quicker...
What are your thoughts?
Thanks for posting the tests!
next prev parent reply other threads:[~2023-08-18 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 15:22 [PATCH RFC net-next v1 0/2] selftests/dpll: DPLL subsystem integration tests Michal Michalik
2023-08-17 15:22 ` [PATCH RFC net-next v1 1/2] selftests/dpll: add DPLL module for integration selftests Michal Michalik
2023-08-17 15:22 ` [PATCH RFC net-next v1 2/2] selftests/dpll: add DPLL system " Michal Michalik
2023-08-18 21:08 ` Jakub Kicinski [this message]
2023-08-21 9:32 ` Michalik, Michal
2023-08-21 21:13 ` Jakub Kicinski
2023-08-24 8:59 ` Michalik, Michal
2023-08-24 15:49 ` Jakub Kicinski
2023-08-25 19:06 ` Michalik, Michal
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=20230818140802.063aae1f@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=arkadiusz.kubalewski@intel$(echo .)com \
--cc=bvanassche@acm$(echo .)org \
--cc=jiri@resnulli$(echo .)us \
--cc=jonathan.lemon@gmail$(echo .)com \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=michal.michalik@intel$(echo .)com \
--cc=milena.olech@intel$(echo .)com \
--cc=mschmidt@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=poros@redhat$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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