DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Etelson, Gregory" <getelson@nvidia.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
	"Yoan Picchi" <yoan.picchi@foss.arm.com>,
	"Jeremy Spewock" <jspewock@iol.unh.edu>,
	"Patrick Robb" <probb@iol.unh.edu>,
	"Luca Vizzarro" <Luca.Vizzarro@arm.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, dev@dpdk.org
Subject: Re: DTS testpmd and SCAPY integration
Date: Mon, 22 Jan 2024 18:31:55 +0100	[thread overview]
Message-ID: <2127794.bB369e8A3T@thomas> (raw)
In-Reply-To: <8dc41944-3ee6-48d0-b1e6-ff086e97aa12@arm.com>

08/01/2024 13:10, Luca Vizzarro:
> Your proposal sounds rather interesting. Certainly enabling DTS to 
> accept YAML-written tests sounds more developer-friendly and should 
> enable quicker test-writing. As this is an extra feature though – and a 
> nice-to-have, it should definitely be discussed in the DTS meetings as 
> Honnappa suggested already.

I would not classify this idea as "nice-to-have".
I would split this proposal in 2 parts:
	1/ YAML is an implementation alternative.
	2/ Being able to write a test with a small number of lines,
	reusing some commands from existing tools,
	should be our "must-have" common goal.

Others have mentioned that YAML may not be suitable in complex cases,
and that it would be an additional language for test writing.
I personnaly think we should focus on a single path which is easy to read and maintain.
For the configuration side, YAML is already used in DTS.
For the test suite logic, do you think we can achieve the same simplicity
with some Python code?

We discussed how to progress with this proposal during the CI meeting last week.
We need to check how it could look and what we can improve to reach this goal.
Patrick proposes a meeting this Wednesday at 2pm UTC.



  parent reply	other threads:[~2024-01-22 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26  7:31 Etelson, Gregory
2024-01-08  1:55 ` Honnappa Nagarahalli
2024-01-08  6:10   ` Etelson, Gregory
2024-01-08 17:36     ` Honnappa Nagarahalli
2024-01-18 12:32       ` Juraj Linkeš
2024-01-19 20:01         ` Patrick Robb
2024-01-08 12:17   ` Luca Vizzarro
2024-01-08 17:35     ` Honnappa Nagarahalli
2024-01-08 12:10 ` Luca Vizzarro
2024-01-08 17:23   ` Etelson, Gregory
2024-01-22 17:31   ` Thomas Monjalon [this message]
2024-01-23  3:42     ` Honnappa Nagarahalli
2024-01-23  8:50       ` Thomas Monjalon
2024-01-23 18:26         ` Jeremy Spewock
2024-01-28 13:44           ` Gregory Etelson
2024-01-30 22:03             ` Patrick Robb
2024-01-31  7:42               ` Etelson, Gregory
2024-02-14 17:27                 ` Gregory Etelson
2024-02-19  5:08                   ` Patrick Robb
2024-02-20 13:35                     ` Gregory Etelson

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=2127794.bB369e8A3T@thomas \
    --to=thomas@monjalon.net \
    --cc=Luca.Vizzarro@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=probb@iol.unh.edu \
    --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).