<div dir="ltr">##################################################################### 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: <a href="https://www.dpdk.org/event/dpdk-summit-2025-prague/">https://www.dpdk.org/event/dpdk-summit-2025-prague/</a> * git apply patch fails for next-dts * Cody Cheng who works on UNH CI Testing can resolve this. * 1. Verify <a href="https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py">https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py</a> requires no updates for next-dts * 2. Add next-dts to the branches dict in <a href="https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py">https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py</a> * 3. Submit to <a href="mailto:ci@dpdk.org">ci@dpdk.org</a> 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</div>