test suite reviews and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dts@dpdk.org, dev <dev@dpdk.org>, ci@dpdk.org
Subject: Re: DTS WG Meeting Minutes - June 20, 2024
Date: Tue, 25 Jun 2024 15:31:42 -0400	[thread overview]
Message-ID: <CAJvnSUA1+PCry7CPz7p5ePiMbP1M-EUDSueqQxP4N5SvxtdgNg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8zbEZdBrYB9t3c0Vctc-CzS+6ADrtuNRfZDgJWkNJXGMA@mail.gmail.com>

On Fri, Jun 21, 2024 at 3:00 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> Hello guys,
>
> On Thu, Jun 20, 2024 at 6:32 PM Patrick Robb <probb@iol.unh.edu> wrote:
> > * DPDK Summit Montreal
> >    * Possible CFP topics for DTS:
> >       * How to write a testsuite. This could be a simple lightning
> > talk which shows how we wrote one of the testsuites we are working on
> > now.
> >       * Luca is interested in giving this talk
>
> It would be cool too if it goes with a crash course about how to setup
> and start DTS (helloworld).
> This may be a bit like reading the existing doc, but it could help
> people cross the initial barrier of touching something new to them.
>
> If it is short enough, it can go in the "writing a testsuite" talk,
> otherwise make it a preliminary talk?
>

+1

There are also some policy changes for the new DTS framework which it
wouldn't hurt to explain, example: password auth to the traffic gen
and DUT nodes is banned and we run from containers so you have to
mount your ~/.ssh into the container. It's all explained in the README
and the docker command given, but not everyone knows containers very
well so it wouldn't hurt to run through this stuff as they could trip
up some people who are new to DTS.

      reply	other threads:[~2024-06-25 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 16:32 Patrick Robb
2024-06-21  7:00 ` David Marchand
2024-06-25 19:31   ` Patrick Robb [this message]

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=CAJvnSUA1+PCry7CPz7p5ePiMbP1M-EUDSueqQxP4N5SvxtdgNg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    /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).