November 13, 2025

Attendees
   1. Patrick Robb
   2. Andrew Bailey
   3. Aaron Conole
   4. Luca Vizzarro
   5. Paul Szczepanek
   
Minutes

General Announcements
   * Release Candidate 3 (RC3) will be released on Monday
   * Patrick to present the proposal for new DTS work to DPDK Governing board on Tuesday. The focus of the work would be cryptodev, virtio, and flow offload testing, per discussion with tech board. Other areas of focus are:
    * Adding further QoL improvements or documentation to facilitate single host DTS runs
    * Further reduce the lines required for testsuites or otherwise simplify the testsuite writing process
CI Status

AWS Lab
   * None
   
UNH-IOL Community Lab
   * SPDK has a build failure on their DPDK branch which they have been slow to resolve, which was causing all new patches to get WARNs for their SPDK build job. So, tech board instructed us to disable the SPDK build on per-patch testing and leave it enabled for nightly builds of mainline. In the future when SPDK branch is in a good state we can revert.
   * We had some downtime for ACVP FIPS testing last week, due to our certificate with NIST expiring. We have renewed our certificate as of end of last week and caught up on results.
   * For our new windows server 2025 build machine, Clang builds with mlnx devx are successful but MSVC is not. After switching to the MSVC developer shell, it appears that Meson is not using the MSVC compiler, which might be the issue. Anyhow, Andre from Microsoft is helping in this thread: https://inbox.dpdk.org/ci/CAJvnSUDtn4e0k3TNFD-jWYHdOhw-jSui2faABMveUmK9gEbsWw@mail.gmail.com/T/#u
   * Runs of the single core forwarding test will be moved over to new DTS from legacy DTS after this release (as that testsuite is being merged in for 25.11)

Intel Lab
   * Patrick emailed them about a build failure on one of his patchseries: https://inbox.dpdk.org/ci/f7tbjlej6me.fsf@redhat.com/T/#t
    * They are excluding doc/* when applying patches because doc/* changes may conflict with the main tree
    * Does proper usage of dpdk-ci/pw_maintainers_cli.py mitigate this issue?
    * Patrick can ask about the reasons why they have to exclude the doc dir

Github Actions Robot
   * None

Loongson Lab
   * None

DTS Improvements & Test Development
   * Virtio testsuite is merged
   * Single_core_forward_perf:
    * Sent a v7 (should be final)
    * Contains a missing SPDX license tag
    * Includes appending c_args="-DRTE_NET_INTEL_USE_16BYTE_DESC" to mesonargs when using an ice driver NIC (required for the best throughput)
    * https://patchwork.dpdk.org/project/dpdk/patch/20251113012732.1059669-4-probb@iol.unh.edu/
    * -The Intel doc build fail is included here, but as discussed previously this is a false failure
   * UNH lab to pick up moving over more of the existing framework calls to the testsuite API during 26.03
    * Otherwise, we need to document the current state of API in dts.rst for this release. That should be the final patch we send, and should be minimal so that we can merge it soon.
   * Thomas recommended that we rename some testsuites to be more clear, which has been ticketed.
   * QinQ testsuite:
    * Looks good, Patrick to do final testing
   * DTS check format script:
    * https://patches.dpdk.org/project/dpdkNov. 13, 2025, 1:27 a.m. UTC/patch/20251106181355.209706-1-dmarx@iol.unh.edu/
   * Will start drafting the 26.03 roadmap next Thursday at the DTS meeting
   * When pydantic is installed on your environment that you build DPDK on, it shows warnings for /dts/. Although this is not a part of how docs are built in CI, it is ideal if we can resolve these warnings. Patrick to look.

Any other business
      * The November 27 meeting is on American Thanksgiving, so it will be cancelled.