DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: DPDK Community CI Meeting Minutes - April 28, 2022
Date: Thu, 28 Apr 2022 17:34:51 -0400	[thread overview]
Message-ID: <CAOE1vsOYc1+w3Q6H6MmcHU-j30k0Hp1F4txiB5Bo4LNt-b8V_A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3354 bytes --]

April 28, 2022

###########################################################
Attendees

1. Lincoln Lavoie
2. Juraj Linkeš
3. Michael Santana
4. Ali Alnubani
5. Nathan Southern
6. Thomas Monjalon

###########################################################
Agenda

1. General Announcements
2. CI Status
3. Test Development
4. Any other business

###########################################################
Minutes

===========================================================
General Announcements

* There are a number of open patches on the dpdk-ci repo that need review.
Thomas volunteered to look at them this afternoon.
* User summit is planned for September (3 day event, 1 day workshop, 2 day
presentations), one potential topic for the CI space is an update /
overview of the DTS improvements and how developers can support / leverage
that testing.  The workshop day is open for proposals (i.e. hackfest focus,
group development, training, etc.), note the room is big enough to support
2 to 3 groups.

===========================================================
CI Status

-----------------------------------------------------------
UNH-IOL Community Lab
* UNH-IOL increased the disk space for the 3 container runners (unit /
compile / abi testing).
* FIPS discussion has continued on the dev list, with a community member
volunteering to take some other algorithms that Brandon hadn’t updated yet.
* Still working on the Arm ampere server deployment.  Owen was
troubleshooting some stability issues for the DTS test cases on those
systems, before we enable the upstream reporting.  This will enable both
the functional and performance bare-metal testing.
* Hardware came in for the Broadcom host repairs, Jeremy has been working
to reinstall the OS on the new systems and get those configured to run DTS
testing again.

-----------------------------------------------------------
Intel Lab

* No updates.

-----------------------------------------------------------
Github Actions / OBS

* No update on Github actions.
* Future work still underway for enhancements to the zero-day bot, need to
update podman on the systems, which is going to take a little longer.
* No action on OBS.
* OBS does provide aarch64 systems, which is missing in Github Actions
coverage.
* Arm was looking into providing resources for Github Actions, but that
work got stalled a couple of months ago.  Juraj can look into this with the
arm folks, just to get a check on the status, etc.

===========================================================
Test Development

*
https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit#
* Identified the first 4 areas to propose as merges into the DPDK main
repo.
* DTS will have the future-dts branch, which will be used for CI testing
(i.e. incoming code changes), to keep the DTS in DPDK main stable.  Team
will need to define a merge strategy for how stable changes are merged into
DPDK main.

===========================================================
Any other business

* Next Meeting: May 12, 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: 4339 bytes --]

                 reply	other threads:[~2022-04-28 21:35 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=CAOE1vsOYc1+w3Q6H6MmcHU-j30k0Hp1F4txiB5Bo4LNt-b8V_A@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).