===================================================================== CI Status
--------------------------------------------------------------------- UNH-IOL Community Lab
* Periodic testing is now added for 22.11 LTS release, and for the 22.11-staging branch of dpdk-stable. * David notified us on Slack about an issue with the incorrect commit urls being assigned to our tarballs acquired for dpdk-stable testing. This does not affect testing accuracy, but it is annoying, and I will apply the fix for that later today. * Environment created for ZUC & Snow3G PMD unit tests, which have been manually run successfully. The team is currently building a Jenkins pipeline to get this online. * After touching base with Dell support again about the RAID controller on the Ampere test bed, they determined a replacement was in order and are shipping on to the lab. * Owen has brought Kmod testing against linux-next to production * ABI testing rollout pending updates to lab code / scripts or resolution of the conversation about 22.11 tag.
* The maintainer for next-broadcom may be inactive - a bugfix applied to main two months ago was not pulled to next-broadcom, and Lijuan is unable to get a response from the maintainer on this. * What does the timeline look like for 19.11 EOL? There will be one more (final) release next week. * Intel CI Lab has some ideas for long term support testing - in the old days only the latest revision of a branch would be tested - Intel is considering also permanently testing the very first version of a release (like 22.11.0). Some customers may always stick to using the initial version of a release.
* There may be some problems with the test-report mail server. Some emails from Loongson with test results have been blocked. * Ali: “It seems that the emails have been getting rejected by the mailing list's server since Tuesday because loongson's mail server was detected in a data set for addresses associated with spam. I just double checked and it seems the address was removed from the spam list. Can you please try to resend?”
* Aaron has merged a change from David which adds some series dependencies support to GHA-Robot * Aaron having a meeting with Rashid Khan regarding how the tech board can get responses back to UNH regarding the SOW
===================================================================== DTS Improvements & Test Development
* Work continues on the hello world test case * Further discussion needed regarding how DTS handles failures - currently whenever a failure occurs anywhere in the process it is caught and recorded, then DTS moves on. It is a problem when it’s unclear whether a failure is caused by DTS or DPDK - DTS team wants to make the feedback from failures more clear, and obviously just make DTS more stable in general. * Owen is interested in adding exit code to DTS for additional feedback on failures. Juraj will follow up with Owen to figure out how exactly this can be best implemented for CI testing purposes. * How can we deal with multiple failures at the same time? Can there be a hierarchy of exit codes? * One idea is to place a higher priority on on failures from DPDK as opposed to a DTS failure
===================================================================== Any other business
* Next meetings: December 22, January 5, sticking to the normal schedule. * December 28th DTS meeting will be canceled as Honappa is on sabbatical until January 3rd. * Tech board meeting is on January 14th for UNH feedback
