From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DTS Meeting Minutes - April 10, 2025
Date: Fri, 11 Apr 2025 15:39:11 -0400 [thread overview]
Message-ID: <CAJvnSUC3sqE5jTY52Lu-WYmjnjSe_AQMjWh2k=kyCtxqYY+Raw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
#####################################################################
April 10, 2025
Attendees
* Patrick Robb
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Discussion
* DTS 25.07 roadmap emailed out:
https://inbox.dpdk.org/dev/CAJvnSUCB4wicXzKsgewF70dgaoE=AoFpCbzzPr0nABwYLvgU1g@mail.gmail.com/T/#u
* We will track the work during the release using the roadmap status
google doc:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit?tab=t.0
* UNH Lab: Dean updated our jenkins script which runs the DTS runner docker
image (with the main.py entrypoint) so that we collect the DTS exit code
and can get automatically alerted when there is a DTS framework/internal
error in our CI. We made this change since we had some test runs silently
failing last week due to a tarball naming conflict.
=====================================================================
Patch discussions
* Paul merged the patch adding the new async sniffer:
https://git.dpdk.org/next/dpdk-next-dts/commit/?id=c933d60a7f8696695eb08ae655f2d809aedc29d5
* Rte_flow: We will need to get clarity from the flow maintainer on what
patterns/rules represent the core functionality and should be a part of the
flow testsuite.
* Dean has drafted an email to this effect, which should go out today.
* Performance tests TG support (TREX):
* Nick is ironing out some bugfixes, but we should have an RFC by the
end of his shift on Friday
* Reviews needed! Patrick and Dean should do this Thursday/Friday.
* Packet capture testsuites:
https://patchwork.dpdk.org/project/dpdk/list/?series=34950
* RSS testsuites:
https://patchwork.dpdk.org/project/dpdk/list/?series=34713
* Shell refactoring patchseries:
https://patchwork.dpdk.org/project/dpdk/list/?series=34865
=====================================================================
Bugzilla discussions
* Reminder: As you begin work on roadmap items, ensure that there is a
bugzilla ticket created which tracks that work
=====================================================================
Any other business
* Next meeting is Apr 24, 2025
[-- Attachment #2: Type: text/html, Size: 2909 bytes --]
reply other threads:[~2025-04-11 19:43 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='CAJvnSUC3sqE5jTY52Lu-WYmjnjSe_AQMjWh2k=kyCtxqYY+Raw@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).