DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS WG Meeting Minutes - January 16, 2025
Date: Thu, 13 Mar 2025 19:01:25 -0400	[thread overview]
Message-ID: <CAJvnSUC1rdADyLAdFSY992WtXAyboqVKLdTi=+jvyrYx3vOc1Q@mail.gmail.com> (raw)

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

#####################################################################
January 16, 2025
Attendees
* Patrick Robb
* Cody Cheng
* Ian Stokes
* Dean Marx
* Paul Szczepanek
* Luca Vizzarro
* Thomas Wilks

#####################################################################
Minutes

=====================================================================
General Discussion
* DPDK Summit will be May 8-9 in Prague:
https://www.dpdk.org/event/dpdk-summit-2025-prague/
* git apply patch fails for next-dts
   * Cody Cheng who works on UNH CI Testing can resolve this.
   * 1. Verify
https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py
requires no updates for next-dts
   * 2. Add next-dts to the branches dict in
https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py
   * 3. Submit to ci@dpdk.org for review.
* Failing existing tests due to scapy
   * Luca observed DTS failing due to errors at packet creation. This may
be due to updating Scapy, which may have brought in a small API change.
      * Nick from the UNH team should try to recreate this, share output on
the dts-dev slack to sync with the ARM guys and confirm it is the same,
* Reviews are more important than new patches right now - we still have a
backlog which we need to review and merge to our next branch.
* DTS Single node Deployments:
   * By running TG and DUT as one system, this reduces the burden for
developers to run DTS using only 1 board. This probably reduces no
limitations for functional tests.
   * Scapy asyncsniffer will never init condition properly when running on
a single system
   * Patrick to make ticket so we can start tracking what the issues are
* DTS internal API:
   * Paul was trying to write docs for the DTS “user” (test developer).
   * What should be exposed to the developer for testsuite
      * Testsuite class should be exposed
      * Logger, for instance, should not directly be used (leveraged only
by framework), but it is located at the same path as TestSuite.
      * Create a top level dir for all the modules that users should use
directly.
      * Seconded by Ian, who ran into this as a new user who did not know
which
   * Currently we have no restrictions on DTS API updates during regular
release dev cycles.

=====================================================================
Patch discussions
* Patchseries merged this week:
   * Dynamic config testsuite
   * fix pass rate edge case in results json
   * Hello_world
   * unified  packet testsuite
      * Is it 1:1 with legacy DTS? If so, copyrights should be brought over.
      * Is nvgre deprecated in DPDK? This was removed in the new testsuite.
* Queue Start Stop was updated this week to change how deferred start is
validated (now checks both that port doesn’t start erroneously, and that it
can be updated at runtime
   * Patrick needs to run this and merge it, but he has no more comments
* Jumboframes/mtu_update
   * Initial testcases simply bring up testpmd using –max-pkt-len
(includinig jumboframe MTU), and send packets
   * Final testcases bring up testpmd, update MTU at runtime, send packets
   * CC Ian Stokes on this who has some background in this subject
* Port topology patch:
   * Luca has offered to take this off of Nick’s hands
   * Ian should be CC’d on this

=====================================================================
Bugzilla discussions
*

=====================================================================
Any other business
* If you observe any instabilities or unpredictable behavior in DTS, please
post to the Slack channel.
* Next meeting is Jan 30, 2025

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

                 reply	other threads:[~2025-03-13 23:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJvnSUC1rdADyLAdFSY992WtXAyboqVKLdTi=+jvyrYx3vOc1Q@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dev@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).