From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes - May 12, 2022
Date: Thu, 12 May 2022 09:55:49 -0400 [thread overview]
Message-ID: <CAOE1vsPNfeu+9+0Rh_7Jak26q=djovNFmVESFM3-R3Cx05obpQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4164 bytes --]
May 12, 2022
#####################################################################
Attendees
1. Lincoln Lavoie
2. Aaron Conole
3. David Marchand
4. Juraj Linkeš
5. Michael Santana
6. Lijuan Tu
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* Nothing specific
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Still working to bring the new arm / Ampere systems online, stability
issues in the tester server traced to a failing RAID controller, working
with the arm team to get this through the RMA process.
* This week (May 9 & May 16) are finals, so will have slower progress on
new items, then will transition to summer time (full-time) hours for the
team.
* Fixed an issue with the ABI tests failing (runners were low on disk
space).
* Working to bring the Broadcom NICs back online for DTS functional /
performance testing, on the new hardware. OSed is installed, working to
get DTS installed and running properly.
* Unit testing on Alpine Linux is fixed (22.03 has the fixes), need to
close: https://bugs.dpdk.org/show_bug.cgi?id=756 Need to get this enabled
to report upstream to patchworks.
* Windows unit testing should be coming online as soon as possible, as
upstream / mainline DPDK now supports running the tests. Unit testing needs
to be excluded from LTS testing for now (i.e. older DPDK branches will not
run).
* Windows compile runs have seen a couple of random failures, where the
process seems to end / exit before the actual meson compile starts (log
just ends).
---------------------------------------------------------------------
Intel Lab
* Updating the test beds for the 22.07 release. Found an issue with
compiling the latest, for Ubuntu 22.04, because of libssl-dev errors.
That’s been disabled for the time being. This needs to be reported up to
the dpdk bugzillia.
---------------------------------------------------------------------
Github Actions / OBS
* Redhat needs to plan for an upgrade of the zero-day robot, which will
create a little down-time / gap in the testing. Aaron will send out
notices before the actual work begins.
* Github actions infrastructure had an outage, caused by changes on their
(Github) systems. Aaron and team had deployed a work around, but they
would like to “roll back” to the “correct” code. They’ll leave some of the
work around code in place (future protections).
* Planning to drop Travis CI from the main branch configurations, as it’s
no longer being well maintained / used at this time.
* Probably going to drop efforts on OBS, and focus on working through the
Github Actions infrastructure, as they are having success adding different
containers / OSes through this setup.
=====================================================================
Test Development
* DTS WG Meeting Minutes:
https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit
* Still working on creating / reviewing the first patch series to submit to
the dpdk main repos.
* Some recent patches to DTS are still submitting test case code that
modifies the DPDK main source. The teams all previously agreed this
approach should not be used and work is already started to “undo” past
tests that used this approach.
=====================================================================
Any other business
* Next Meeting: May 26, 2022
* Plans for the DPDK User Space Summit in September? Aiming to have a good
CI “presence” during the event.
--
*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: 5178 bytes --]
next reply other threads:[~2022-05-12 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 13:55 Lincoln Lavoie [this message]
2022-05-13 7:01 ` David Marchand
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='CAOE1vsPNfeu+9+0Rh_7Jak26q=djovNFmVESFM3-R3Cx05obpQ@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).