DPDK CI discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Etelson, Gregory" <getelson@nvidia.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	 Paul Szczepanek <Paul.Szczepanek@arm.com>,
	Luca Vizzarro <Luca.Vizzarro@arm.com>,
	 Yoan Picchi <yoan.picchi@foss.arm.com>,
	Jeremy Spewock <jspewock@iol.unh.edu>,
	 Patrick Robb <probb@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
	 Asaf Penso <asafp@nvidia.com>,
	Maayan Kashani <mkashani@nvidia.com>
Subject: Re: DTS testpmd and SCAPY integration
Date: Thu, 18 Jan 2024 13:32:39 +0100	[thread overview]
Message-ID: <CAOb5WZarn-+==hyeCeyfOV=eZi=EH5OAxuCRZ0mfijmm88v2jg@mail.gmail.com> (raw)
In-Reply-To: <DBAPR08MB581418ECB454AADFF4939982986B2@DBAPR08MB5814.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

Hi folks,

Let me summarize the yesterday's discussion in a few keys points:

   - Greg's proposal aims at simplicity and is useful mainly for test cases
   which can be written in a few minutes. More complex test cases are not
   suitable for the YAML approach.
   - The above implies that the YAML based test cases would be supported
   alongside the existing approach. This fast way to implement simple test
   cases would likely be a valuable addition.
   - The big picture idea behind the YAML test cases is to take an
   application with interactive input, send commands, collect output and
   compare the output with expected string(s).
   - Greg may be able to make the code available and may assess how to
   integrate it with DTS.

Regards,
Juraj

On Mon, Jan 8, 2024 at 6:36 PM Honnappa Nagarahalli <
Honnappa.Nagarahalli@arm.com> wrote:

> <snip>
>
> >
> > Hello Honnappa,
> >
> > [snip]
> >
> > > Hi Gregory,
> > >        I do not fully understand your proposal, it will be helpful to
> join the DTS
> > meetings to discuss this further.
> > >
> >
> > Agree, let's discuss the proposal details during the DTS meeting.
> >
> > > YAML has wide support built around it. By using our own text format,
> we will
> > have to build the parsing support etc ourselves.
> > >
> > > However, YAML is supposed to be easy to read and understand. Is it
> just a
> > matter for getting used to it?
> > >
> >
> > I selected YAML for 2 reasons:
> >    * Plain and intuitive YAML format minimized test meta data.
> >      By the meta data I refer to control tags and markup characters
> >      that are not test commands.
> >    * YAML has Python parser.
> I have mis-understood your proposal. I agree with your above comments.
> +1 for the proposal.
>
> >
> > Regards,
> > Gregory
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 2385 bytes --]

  reply	other threads:[~2024-01-18 12: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š [this message]
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
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='CAOb5WZarn-+==hyeCeyfOV=eZi=EH5OAxuCRZ0mfijmm88v2jg@mail.gmail.com' \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Luca.Vizzarro@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=asafp@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=jspewock@iol.unh.edu \
    --cc=mkashani@nvidia.com \
    --cc=nd@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --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).