February 19, 2026
Attendees
1. Patrick Robb
2. Aaron Conole
3. Matthew Labrecque
Minutes
General Announcements
* AI Code Review:
* Andrew has reviewed the python scripting for the anthropic client
* Patrick is reviewing currently
* Matt Labrecque and Patrick to meet and run the scripting, produce
a review from Anthropic
* Current plan is to send the AI reviews to the test-report mailing
list - will be picked up by Patchwork
* Can tweak later as needed
* Need to write up the formal “rule set” and document that
somewhere. DPDK testing page?
* UNH Team to send a dpdk-web patch with the rules:
https://core.dpdk.org/testing/
* The UNH team can start setting up the Jenkins scripting now.
There is no need to wait for Stephen’s scripting to get merged into
DPDK.
* DPDK Stockholm:
* Stephen and Aaron to give a talk about the AI Code Review
* Patrick giving a talk about DTS integration into developer
workflow and the new flow offload testsuite
* 1 week CFP extension
* RC1 was released earlier this week
* CI project on Patchwork:
* Some patches wer not tagged correctly (accepted, superseded,
deferred, etc.) and Aaron has updated these statuses
* Aaron also working on some scripting so that when he applies a
patch, the patch status will update at the same time
CI Status
AWS Lab
* None
UNH-IOL Community Lab
* PRs under review for using buildtools/get-meson-version.py for
FreeBSD and Windows pipelines.
* Let’s do a dry run run of these and check for correct behavior
* Matt to check in on the powershell version on server 2025 (the
only windows version we test with, as we use only latest)
Intel Lab
* None
Github Actions Robot
* Aaron working on the code coverage automation
Loongson Lab
* None
DTS Improvements & Test Development
* Cryptodev:
* V3 is out, Patrick to review:
https://patchwork.dpdk.org/project/dpdk/list/?series=37360
* The DTS patches which we have merged so far this release were merged to RC1
* Otherwise, RC2 should release March 5. Aiming to have all new
testsuites merged by that time
* Flow Offload:
* We did an internal review and reached the conclusion that real
world applications will write flow rules that match on 1-2 protocols
for a packet, not more than that. Got a list of “realistic” scenarios
to test for and applying those to the flow offload testsuite. It will
still test a broad set of hundreds of flow rules, but these will be
more targeted towards real use cases.
* Code Coverage Reports: Working on a patch now that adds a config
option that will add the code coverage argument to the meson setup
command.
* Question: If we start and stop testpmd on the SUT N times during
a testrun, can we have the coverage reports from all of those testpmd
runs be “appending” and provide a total code coverage report, or will
it produce a large number of reports which we cannot merge together in
a way which is reasonable for humans to read? Need to check this out.
Any other business
* Next meeting is Mar 5, 2026
