From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes - February 3, 2022
Date: Thu, 3 Feb 2022 09:32:43 -0500 [thread overview]
Message-ID: <CAOE1vsMS-qHXq=eBrceOEvQZqfqE=svVYQEsswzcY4kxtV3rsg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2717 bytes --]
February 3, 2022
#####################################################################
Attendees
1. Lincoln Lavoie
2. Brandon Lo
3. Ali Alnubani
4. Maxime Coquelin
5. Michael Santana
6. Aaron Conole
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* None
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Unplanned maintenance
* There was a significant CVE on polkit last week that required downtime
to implement a patch across all systems in the lab.
* FIPS
* Changes to DPDK and DPDK-CI are waiting for review.
* Internal scripts to deploy FIPS testing are completed.
* Going to only run this test on crypto changes, based on where the
patch “applies” within the directory tree.
* FreeBSD 13 compiled and ABI disabled
* Looking into why FreeBSD 13 now fails to compile tarballs that
compiled before. Only change to the VM was rebooting during the
maintenance process for recent CVE.
* VirtIO
* Scripts for generating VM are complete, and need to be submitted as a
patch for DTS.
* Smoke tests and basic cases are ready to be turned on in CI, just need
to get this enabled across the different bare-metal platforms.
* Maxime Coquelin offered to help with any issues encountered in setting
up the tests for virtIO.
* RTE Flow
* Still working on the rollout of this testing. This has driven a
number of changes / patches needed into DTS, as things have changed since
this was originally developed.
---------------------------------------------------------------------
Intel Lab
* Lunar New Year Holiday
---------------------------------------------------------------------
Github Actions / OBS
* No Updates
=====================================================================
Test Development
* DTS WG continues to meet and move forward. Aiming to merge DTS into the
DPDK main repo with tests that are currently used in CI as part of the
22.07 release.
=====================================================================
Any other business
* Next Meeting: February 17, 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>
[-- Attachment #2: Type: text/html, Size: 3628 bytes --]
reply other threads:[~2022-02-03 14:32 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='CAOE1vsMS-qHXq=eBrceOEvQZqfqE=svVYQEsswzcY4kxtV3rsg@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).