From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, dts@dpdk.org
Subject: Community CI Meeting Minutes - November 14, 2024
Date: Sun, 15 Dec 2024 23:09:49 -0500 [thread overview]
Message-ID: <CAJvnSUA5r2d28o7Dfx0017QNFFQEnD775wLM61dmRoGSTn_bNw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]
#####################################################################
November 14, 2024
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Announcements
* Bruce raised an idea on slack of provide initial pending status for all
labs from one centralized job (can be run by UNH)
* Meeting time will be moved by 1 hour to accommodate for daylight savings.
The meeting time will be 14:00 UTC.
* Dts roadmap:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit?tab=t.0
* RC3 is out next Tuesday
* Thomas has indicated he may pull from next-dts today
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Cody at UNH is dry running tests on the new CN10K cryptodev (legacy) DTS
testcases
*
https://patchwork.dpdk.org/project/dts/patch/20241030164419.3164992-1-gpalanethra@marvell.com/
* We have merged to next-dts a series which adds detailed testrun json
output, which we have been needing in order to meaningfully run DTS in CI.
Once this series is pulled into mainline (ideally rc3), UNH should be able
to start reporting results to the mailing list from new DTS.
* Adam’s v2 patchwork patch for depends-on has had a review from the
maintainer and got some light comments - he is working on the v3 now.
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Github Actions
* None
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* Testsuites merged this week:
* Pydantic data validation
* L2fwd testsuite and testsuite helper functions
* Async sniffer bugfix
* Patrick will be continuing to merge some testsuite patches today and
tomorrow
* Testsuite documentation style:
* Current testsuites have different docstring sections for the testcase
functions. One approach used is specifying “steps” and “verify” content for
each testcase. We should move to this approach for all testsuites in DTS.
=====================================================================
Any other business
* Next Meeting Nov 28, 2024
* Marvell crypto test legacy DTS patch was discussed - this is being
reviewed by Patrick
[-- Attachment #2: Type: text/html, Size: 3026 bytes --]
reply other threads:[~2024-12-16 4:12 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=CAJvnSUA5r2d28o7Dfx0017QNFFQEnD775wLM61dmRoGSTn_bNw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@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).