From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: Community CI Meeting Minutes - January 23, 2025
Date: Thu, 13 Mar 2025 19:04:29 -0400 [thread overview]
Message-ID: <CAJvnSUBnno0Dp+DU27jiLRg53td-CB6mZf16e_AcYyVMn6YSnQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4130 bytes --]
#####################################################################
January 23, 2025
Attendees
. Patrick Robb
. Aaron
. Paul Szczepanek
. Andre Muezerie
#####################################################################
Minutes
=====================================================================
General Announcements
* Aaron raised patch volume and public lab test capacity at tech board
yesterday, and this will be a discussion item at the next tech board
meeting on 02/05
* CI testing should not be a replacement for developers testing their
code before submission to the mailing list. When people submit patches in
high volume with minimal testing, it can create a testing queue which
worsens the experience for everyone.
* For the linux kernel project, developers are “rate limited” to 1
patchseries per 24 hours
* If your patch causes a build failure, you should not resubmit for
some longer period (maybe a week)
* There may be some opportunities to make developer testing easier
* For instance, it may be possible to add a GHA cross compile to
arm64 which would allow developers to fork the repo, get cross compile
tests for their patches
* Andre has started working on DPDK at Microsoft and has joined the meeting
to get to know the CI processes
* Patrick should check which build toolchains are in use (should be all
3 supported for windows) and email this to andre afterwards.
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* The new ARM Grace-Grace server has shipped, patrick has the tracking #,
and it is expected to be delivered to UNH tomorrow January 24.
* NICs will be moved over to the Grace server according to the migration
plan which was shared out to the governing board and tech board last year
* David helped add the “next-dts-for-main” branch to github, which mirrors
the next-dts branch from dpdk.org.
* Still require a review and merge from Aaron for
https://patchwork.dpdk.org/project/ci/patch/20250116221112.19794-1-ccheng@iol.unh.edu/
which simply adds a mapping for this branch in the CI patch apply script
* New DTS in CI testing:
* Patrick is adding configs for additional NICs - aiming to turn this on
early next week. Most likely to start with a few testsuites and then scale
up from there.
* Dashboard search feature has been added, allowing users to search for
test results by patchwork series id OR by patch name keywords
* https://lab.dpdk.org/results/dashboard/
* Patrick to check with Adam about the depends-on series for the patchwork
project
* Latest we heard was that there were no additional comments from the
maintainer and that it was expected to be merged in the current patchwork
release cycle
* Cody is adding a cross compile job for x86 32 bit
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Github Actions
* Aaron has resurrected the Cirrus CI support patch - addressing some
comments and will submit a new patchseries version tomorrow or next week.
* Zero day bot will connect with Cirrus server, which supports freebsd
and windows
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* Refactor configuration series:
https://patchwork.dpdk.org/project/dpdk/list/?series=34355
* Reviewed by Dean
* Nick is reviewing now and will have all comments in by EOD
* Patrick left a few comments for the MTU testsuite, which Nick has
indicated he will incorporate into a v2 and submit by EOD
* Should be possible to merge this “immediately” as the comments were
minimal, and Patrick has tested the V1 across multiple NICs
=====================================================================
Any other business
* Next Meeting Feb 6, 2025
[-- Attachment #2: Type: text/html, Size: 4546 bytes --]
reply other threads:[~2025-03-13 23:08 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=CAJvnSUBnno0Dp+DU27jiLRg53td-CB6mZf16e_AcYyVMn6YSnQ@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@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).