DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes November 18, 2021
Date: Thu, 18 Nov 2021 10:24:34 -0500	[thread overview]
Message-ID: <CAOE1vsPih2mUSH-6+7TpeVOdm+DgBMXKepB6e+fDQZ4dJ8toTg@mail.gmail.com> (raw)

DPDK Community CI Meeting Minutes

Nov 18, 2021

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

1. Lincoln Lavoie
2. Lijuan Tu
3. Thomas Monjalon
4. Aaron Conole
5. Juraj Linkeš
6. Ashley Weltz
7. Michael Santana
8. Ali Alnubani
9. Brandon Lo

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

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

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

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

* Nothing specific to CI this week.

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

---------------------------------------------------------------------
UNH-IOL Community Lab

* Notifications have been enabled from the lab to the DPDK CI list.  This
will occur if hosts, VMs, or services fail within the lab.  Limit is one
notification per object per 24 hours (internally we get notified every hour
24 hours a day).
* Spell check test was disabled per request, techboard requested to change
to testing patch content only (not all documentation).  Working to update
the tooling.  Plan is still to submit this tooling as part of dpdk/devtools
so a patch submitter could add dictionary words and exceptions, asked for
this to go in a V3 to the existing patch.
* Working on aarch64 clang compile and unit testing jobs (runs natively on
aarch64 hardware).  In progress, pipelines are being tested.
* Added clang cross-compile x86_65 -> aarch64, now in production
* Will be adding gcc cross-compile x86_64 -> aarch32, selected for
development.
* SPDK testing is still disabled, while SPDK “catches up” to DPDK changes
(BUG-876).
* Brandon is also still working on FIPS, the maintainers confirmed the
“new” NIST vectors are not compatible with the sample application and they
have just been “reusing” older vectors you can no longer get from NIST
(i.e. email / purchase process).  Investigating adding a CLI flag to load
the new vector format to not break their existing testing.
* Post 21.11 release, we would like to plan downtime to upgrade Jenkins,
this is the follow up to the failed update in September.
* 2022 planning is getting started, if there are tests the community would
like to see put onto the work plan for 2022, now is the time.

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

* Planning downtime for after 21.11 release for lab migration.
* Rerun requests: What is the maximum query rate allowed by patchwork?  The
overall issue is supporting a common mechanism across the different test
infrastructures.  Ali will double check if events could be possible in
patchworks.  Otherwise, we could create a micro-service to do the polling
solution, and that service generates the events.  Could also put a “script
/ bot” between the mailman and patchworks.
* Some “old” patches on patchworks still listed as “new” on patchworks?  CI
systems need to ignore these.  If a lab is “offline” for a time, the “catch
up” needs to account for the date the lab went off-line.  Lab polling
scripts can keep track of the time-stamp they last polled for patches, to
pick up where they left off.

---------------------------------------------------------------------
Github Actions & OBS

* Not much on the OBS side.
* Posted a patch series for Fedora 35, not quite ready for production, need
to check some issues with pull images from docker, etc.  Not ETA for this
yet.  Issues are within Github actions, and not within the control of the
project.

---------------------------------------------------------------------
Arm Lab

* Arm was looking into how they could provide compute resources towards
Github actions, but no more information is available.  Need some additional
information from arm on email and design choices for the proposed updates
to the Github yaml.

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

* DTS improvements group is starting work on the plan to adjust and remove
places where DTS modifies dpdk code.  There are likely to be some patches
for DPDK to “add” requirements for these items.
   * Will also need to plan for how this will impact LTS testing (i.e.
older DPDK code wouldn’t have these changes).
* Some core changes to the framework and will need detailed community
review on those changes to use the dpdk log output to help construct the
reports.  Might be ready next week.
* Next DTS meeting December 1, 2021, 9am EST

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

* Next Meeting: December 2, 2021


-- 
*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>

             reply	other threads:[~2021-11-18 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 15:24 Lincoln Lavoie [this message]
2021-12-01 13:03 ` Ali Alnubani

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=CAOE1vsPih2mUSH-6+7TpeVOdm+DgBMXKepB6e+fDQZ4dJ8toTg@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).