From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org, dts@dpdk.org
Subject: Community CI Meeting Minutes - May 25, 2023
Date: Thu, 25 May 2023 09:46:15 -0400 [thread overview]
Message-ID: <CAJvnSUB5H87_vvv7FiP63hnho_DHE75DmrzogWwfcw0_F9J1ag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3620 bytes --]
#####################################################################
May 25, 2023
Attendees
1. Patrick Robb
2. Lincoln Lavoie
3. Nathan Southern
4. Ali Alnubani
5. Aaron Conole
6. Jeremy Spewock
7. Adam Hassick
8. Lijuan Tu
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. DTS Improvements & Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* DPDK Userspace: Sept 12-13 in Dublin Ireland - Gibson Hotel
* Call for papers date is not set, but will be set in the very near
future per the tech board
* CFP should be finalized by Monday - registration to be done by May 31
* Cfp will be may 31 to june 30th
* Tech board will vote on submissions in early July
* Speaker notifications to go out on July 11th
* Patrick from UNH will be going as well as Aaron Conole
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* The DPDK CI Container Build System which we use to build UNH’s DPDK and
CI ready container images is being upstreamed. Adam submitted a patch
series for it, and the build system will be available on the dpdk-ci repo
pending review from the maintainers.
* To be upstreamed to the dpdk-ci repo:
https://git.dpdk.org/tools/dpdk-ci/
* Makefiles build dockerfiles based on templates according to a set of
env variables set by the user
* Uses oci manifests to utilize arm and x86 images in CI
* 32 bit unit tests on arm systems: This is now online, and runs on the arm
altra bare metal system
* Uses a custom set of unit tests which is actually more extensive than
the fast tests test suite we run elsewhere in our CI (for instance it
includes a subset of the perf test testsuite)
* Can it report with other unit tests or should it have a distinct label
as a 32 bit test?
* UNH’s email DMARC issue is resolved now - we cut the subject line of
test-report emails at 68 characters per Ali’s observation that Mailman was
folding the subject line into multiple lines at 70 characters
* Aaron did take a look at metrics regarding UNH testing
---------------------------------------------------------------------
Intel Lab
* Working on containers - moving some of their test beds to containerization
* Will be used for 23.07 testing, then continue to extend container use
even further in future releases
* Intel is interested in upstreaming some dockerfiles to the dpdk-ci repo
* Just doing routine work to get ready for 23.07
---------------------------------------------------------------------
Loongarch Lab
* none
---------------------------------------------------------------------
Github Actions
* No updates
=====================================================================
DTS Improvements & Test Development
* Juraj Linkeš responded to Jeremy’s RFC about utilizing paramiko to drive
the (allocated for interactive shells) ssh session via channels for dpdk
apps. There are some design issues regarding abstraction which need to be
addressed
=====================================================================
Any other business
* Next meeting is June 8
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 5970 bytes --]
reply other threads:[~2023-05-25 13:46 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=CAJvnSUB5H87_vvv7FiP63hnho_DHE75DmrzogWwfcw0_F9J1ag@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dts@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).