From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes - January 5, 2023
Date: Thu, 5 Jan 2023 10:04:53 -0500 [thread overview]
Message-ID: <CAJvnSUDa5=cMLtbV6jQf_7HUi+bOkZ+74yunJ5Asb_Lo281X2A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2547 bytes --]
January 5, 2023
#####################################################################
Attendees
1. Patrick Robb
2. Min Zhao
3. Lijuan
4. Michael Santana
5. Ali Alnubani
6. Jeremy Spewock
7. Lincoln Lavoie
8. Adam Hassick
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. DTS Improvements & Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* Happy new year!
* Ali: Scheduled downtime for dpdk.org servers this Sunday - Patchwork down
for approx 1 hour
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Our ABI testing coverage has been brought back online
* Ampere Altra: We began activating reporting/saving to the dashboard
yesterday afternoon. It is currently publishing performance results on DPDK
main, and functional tests on all branches. I’ll make the necessary changes
today to activate performance reporting on all branches.
* We are delaying bringing the Zuc/Snow3G unit tests online in order to
rework our testing pipelines and container building approach, which should
bring greater stability to testing going forward
---------------------------------------------------------------------
Intel Lab
* Dpdk 19.11/20.11 LTS versions have reached end of life - testing is ending
* Next broadcom maintainer is still unresponsive - thus there cannot be any
testing on this branch
* Working on preparing for 23.03
* Next meeting is Chinese New Year - Lijuan will be out and there may be
some Intel downtime
---------------------------------------------------------------------
Loongarch Lab
* Duplicate emails were being sent to test-report - this problem has been
resolved
---------------------------------------------------------------------
Github Actions
* N/A
=====================================================================
DTS Improvements & Test Development
* Smoke testing conversations are progressing for new dts
Any other business
=====================================================================
* The next meeting is January 19
--
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: 4609 bytes --]
reply other threads:[~2023-01-05 15:05 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='CAJvnSUDa5=cMLtbV6jQf_7HUi+bOkZ+74yunJ5Asb_Lo281X2A@mail.gmail.com' \
--to=probb@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).