February 1, 2024
#####################################################################
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Thomas Monjalon
4. Juraj Linkes
5. Ali Alnubani
6. Aaron Conole
#####################################################################
Minutes
=====================================================================
General Announcements
* Per mailing list/slack conversation, an important feature to add for the email based retest framework is to trigger a retest, but instead of retesting the original DPDK artifact created for the patchseries, re-apply on latest and retest. Ferruh suggests we include an optional argument “pull”, so if “pull=true” we re-apply on latest, if the argument is omitted or pull=false we do the normal behavior.
* Some community members running automation are still pulling from the dpdk.org git server and need to move to github. People who don’t move will get blacklisted, and then they will move quickly.
* Making periodic test results more visible:
* Would be helpful to list the testing labels matrix for periodic “main” testing on the dpdk.org testing page (or a page under testing).
* After main, we should add all branches, and should display datetime of test and branch name
* Can also extend this to per patch testing. If we only include the latest patch tested, at least that shows all the labels tested.
* Would be helpful to have a more detailed description.
* We can do this in small steps, and just start with periodic testing.
* Is there a problem with testing RFCs? UNH and GHA are not doing it, but should start. It does present a value to maintainers/developers and it probably does not present a testing capacity problem (most come early in a release cycle.)
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Automation for TS-Factory testing is now online at UNH
* Runs on ARM servers, for the XL710 NIC and MLNX CX5
* Runs 1x/month
* Posts results to https://ts-factory.io/bublik/v2/runs
* UNH team is still working on provisioning the new server donated by Intel
* Requesting reviews/comments on Adam’s create artifact script (can be used in ci to leverage the pw_maintainers_cli.py tool for creating DPDK artifacts from new patchseries): https://inbox.dpdk.org/ci/20240118234120.29256-1-ahassick@iol.unh.edu/
* Rebuilding containers for all testing which has an ipsec-mb library dependency (fips, zuc, snow3g) due to the minimal version increasing to 1.4: https://inbox.dpdk.org/dev/20240130142412.2047550-1-venkatx.sivaramakrishnan@intel.com/
---------------------------------------------------------------------
Intel Lab
* No updates from John
---------------------------------------------------------------------
Github Actions
* Will be (within the next week) migrating the VM which runs the robot. The disruption should be about one half day.
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* We held a meeting yesterday for this.
* We have someone at UNH starting now on this project (Nicholas Pratte), so we will see if he can start joining these meetings
* Should update the bugzilla query for DTS to include the priority column so we can sort by that
=====================================================================
Any other business
* In the near future, we should change the week which ci meetings fall on, so that they are on the off week of the DTS meetings
* Thomas will start saving the ci meeting minutes on the website
* Next Meeting: February 15, 2024