From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: CI Community Minutes - January 20, 2022
Date: Thu, 20 Jan 2022 12:13:57 -0500 [thread overview]
Message-ID: <CAOE1vsP3r3ysVaN2KxU6NQXKJHSySPm7-JQmoBMEg0a2OC198Q@mail.gmail.com> (raw)
January 20, 2022
#####################################################################
Attendees
1. Lincoln Lavoie
2. Lijuan Tu
3. Brandon Lo
4. Owen Hilyard
5. Juraj Linkeš
6. Michael Santana
7. Ali Alnubani
8. Henry Nadeau
9. David Marchand
10. Thomas Monjalon
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* No updates
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* FIPS
* Overall refactors to the FIPS validation example application are done,
need to work on a script that handles submitting the results back to the API
* Working to publish the script that interacts with the ACVP API as a
patch to the dpdk-ci repo
* Code should be out for review by the end of next week at the latest.
* DTS upgrades completed across the bare-metal hardware, to roll out
changes (in DTS) to enable RTE Flow testing to be turned on.
* Sending up a patch to DTS to repair an issue with how TRex is started
for the NIC single core (is hardcoded to be different between vendors), v2
patch is being worked on.
* Still working on VirtIO VMs and rolling out the first parts of that
testing. Some parts of the DTS VirtIO tests require updates (i.e. remove
assumptions about physical setup, remove modifications made to DPDK code
during testing, etc.) That DTS update work is proposed as part of the 2022
work plan. Aiming to turn on the “other” virtIO test cases that don’t
require repair by the end of next week. Patch for VM generation should be
up to DTS next week as well.
* VM generation scripts are intended to generate VMs for both x86_64 and
aarch64 platforms, but generation has to be done on the target architecture
(i.e. no cross builds). Generation tested under an emulated VM.
* Should also support PowerPC architecture, but this is not tested.
* Made some tweaks to the 20.11 and 21.11 LTS periodic testing to skip
Alpine Linux tests for 20.11 (not supported, etc.).
* Have a plan to leverage a local GitLab instance to host patch sets as
pull results to enable analysis of changes / deltas for the static analysis
tools. Work on the tool chain to implement that has started. Jenkins can
then use the pull results as the input to the static analysis pipelines
* If this is as successful as we believe it could be, we may be able to
expose the GitLab instance and store the test artifacts alongside the PR
(i.e. link from patchworks or the dashboard could take you to the “PR” for
the patch, where artifacts are available.
* 2022 Planning: DPDK 2022 Work Planning
* Please add feedback to this document ASAP. Lincoln will send a
reminder to the tech board email list well.
* Needs to be finalized by the end of January.
---------------------------------------------------------------------
Intel Lab
* Intel CI is recovered since the upgrades and has been running since Jan
7, 2022.
* Upgraded refreshed OSes and prepared for the 22.03 release.
* Planning for the upcoming Chinese New Year holiday (end of January /
early February).
---------------------------------------------------------------------
Github Actions / OBS
* No updates.
=====================================================================
Test Development
* DTS WG meeting (January 19, 2022)
* Work is still ongoing to remove places where DTS modifies DPDK code
during testing.
* Request for comments on the DTS contribution guidelines (
https://docs.google.com/document/d/1G7_AEA-4MAd88bxjfP-IOcIy_6mnrMz3HCsUI8e-NN4/edit?usp=drive_web&ouid=111054014354037689830),
based on DPDK guidelines, with additions for python.
* Some code was found with GPL license headers and other work with no
identified license header. Honnappa is raising this with the tech board.
* Investigating documentation generation tooling in prep for moving into
DPDK repos.
* Aiming on moving in the framework and CI test suites to the DPDK CI
repo by the 22.07 release.
* Looking into pinning the python version to 3.6 for DTS (requesting
comments via email).
=====================================================================
Any other business
* Next Meeting: February 3, 2022
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
reply other threads:[~2022-01-20 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOE1vsP3r3ysVaN2KxU6NQXKJHSySPm7-JQmoBMEg0a2OC198Q@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).