Community CI Meeting Minutes - May 29, 2025

Community CI Meeting Minutes - May 29, 2025

[Patrick Robb]

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

#####################################################################
May 29, 2025
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Aaron Conole
4. Manit Mahajan

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

=====================================================================
General Announcements
* LTS branches (with backports), which were previously only available on
the Github dpdk-stable repo, are now available on the github DPDK repo.
Example: https://github.com/DPDK/dpdk/tree/24.11
* Patrick still needs to send out a survey to CI meetings folks for finding
an agreeable new meeting timeslot.
   * In order to facilitate both Europe, Asia, and North America, we may
have to alternate the meeting time.

=====================================================================
CI Status

---------------------------------------------------------------------
UNH-IOL Community Lab
* Cody brought the x86 Intel e810 100G single core forwarding test back
online.
   * Necessitated making the TREX traffic profile homogeneous as the
traffic mix used before was causing issues with the TREX software.
* New environment info update process:
   * Runs once every 48 hours when there is a periodic (no patch) run on
dpdk mainline
   * Added a stage to all our testing pipelines which will run a python
subprocess script to collect software information. Then, sends a PATCH http
request to our DPDK dashboard, which updates the database.
   * Collects these values from the system:
      * Compiler version
      * Kernel version
      * Kernel cmdline
      * Os distro
   * Followup values we want to grab in the future:
      * Libc version
* Working on some internal tooling to help our maintenance:
   * Refactoring our ansible playbooks so that we have a larger set of
discrete provisioning playbooks instead of our monolithic playbook which we
have been managing for years, and is becoming a maintenance burden.
* Currently we have 2 racks at UNH set aside for DPDK servers, one is
completely full and the other half full. We had a couple parties at DPDK
Prague offer to help fill the remaining 24U in the second rack, and we are
following up with these parties.

---------------------------------------------------------------------
Intel Lab
* None

---------------------------------------------------------------------
Github Actions Robot
* Aaron started looking at changes to the patchwork events API.
   * Adam Hassickshould review the email thread on this and see if he can
suggest any ideas for improving the patchwork API
* There was a little discussion about how developers would benefit from
forking DPDK on github and leveraging the GHA pipelines, which would help
with the simplest type of failures (like just failing build on linux)
* Aaron notes that ovs and netdev are seeing similar issues as DPDK in
terms of developers relying too much on CI, and completely forgoing
personally testing their patches ahead of submission to the mailing list.

---------------------------------------------------------------------
AWS Lab
* No updates, but Patrick will try to find some CI meeting scheduling
solution which will work for Shai.

---------------------------------------------------------------------
Loongson Lab
* It is confirmed that Loongson lab is supporting the email based test
recheck framework. However, we have not synced with Min Zhou about
supporting the rebase={branch} argument for rechecks. Patrick has emailed
on the old loongson recheck support email thread asking for the latest
status.
   * We need to send a patch to the testing page for dpdk.org adding
loongson as a lab which supports this.

=====================================================================
DTS Improvements & Test Development
* README and dts.rst rewrite to simplify user onboarding instructions:
   * Reviewed by Patrick and Paul. Looks good mostly but needs a v2 for
some minor nits, and has a warning which needs to be resolved.
* Reminder - when submitting a DTS patchseries:
   * Run dts-check-format.py, checkpatch, check-git-log.sh, and ideally do
a docs build.
* Rte_flow: Dean has submitted a v2, which adds a flow validate call ahead
of each flow create call.
   * Patrick to review for a v3 or merge.
* Docs patch which adds explanation of per testsuite config file
   * Patrick to review and merge
* dts: use tmp dir and DPDK tree dir
   * Tested and reviewed by Dean
   * Patrick to review and merge
* Improve port handling:
   * Dean has reviewed
   * Paul to merge
   *
https://patchwork.dpdk.org/project/dpdk/patch/20250506131657.1576152-1-luca.vizzarro@arm.com/
* Docs builds are a big burden, as there are lots of warnings:
   * Should be a discussion item at the next meeting
   * If you have ideas on how the process (on the DTS side or the DPDK
side) can be improved to make this less of a maintenance burden, please
bring those to the next meeting

=====================================================================
Any other business
* Next Meeting Jun 12, 2025

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