From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>
Subject: Community CI Meeting Minutes - June 25, 2025
Date: Tue, 8 Jul 2025 18:44:43 -0400 [thread overview]
Message-ID: <CAJvnSUAr78vbPCDnF_xav7Own8d_zgm5cK0ZuWU4+5yzLDCbcw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3634 bytes --]
#####################################################################
June 25, 2025
Attendees
1. Patrick Robb
2. Manit Mahajan
3. Dean Marx
#####################################################################
Minutes
=====================================================================
General Announcements
* Expected RC schedule:
* RC2 - June 27
* RC3 - July 2
* Results from the “when to meet” survey:
https://www.when2meet.com/?30965992-3ijyI
* Basically, options going forward are Tuesdays from 12:00 UTC to 14:00
UTC, Wednesdays from 13:00 UTC to 14:00 UTC, and Thursdays from 12:00 UTC
to 13:00 UTC.
* DPDK-CI Test Recheck script has been updated to capture the “rebase” flag
for rebasing onto specific branches by developer request:
*
https://patchwork.dpdk.org/project/ci/patch/20250611205849.72165-1-probb@iol.unh.edu/
* https://core.dpdk.org/testing/#requesting-a-patch-retest
* CFP for the Santa Clara Summit is closed
* The testing group does not have any talks submitted for this
conference, but Patrick will probably go to attend
=====================================================================
CI Status
---------------------------------------------------------------------
AWS Lab
* Test recheck support plans:
* David noticed some failures due to timeout on the telemetry test, other
CIs run with -t 3 (30s timeout, instead of 10):
* Review on apply failure on .rst files discussion from the previous meeting
UNH-IOL Community Lab
* Apply patchset process: Skipping making a tarball if the patch is a docs
patch only.
* Labeling as “not applicable” on the lab dashboard
* Windows Builds:
* Clang build is not picking up the devx lib file - Patrick needs to
check if this behavior is new.
* WARN/FAIL email reporting error for Windows builds has been resolved.
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Github Actions Robot
* None
---------------------------------------------------------------------
Loongson Lab
* Patchseries recheck support: Min Zhou has tested out the new version of
the get_reruns.py script, and has indicated he will use it to support the
rebase argument.
* When this happens we need to update the DPDK website testing page to
update the supported labs list
=====================================================================
DTS Improvements & Test Development
* README and dts.rst updates are merged.
* Virtual Function testing:
* Packet forwarding from DTS created VFs is working (on Intel)
* Dean is refactoring the existing testsuites to ensure that they will
work for both PFs and VFs
* Performance testing and nic_single_core_perf:
* Removing the usage of Invoke Promise from the V2.
* This time, we start the trex server process and collect PID, then
loop on trying to connect to the trex server process with STLClient, then
kill the trex PID at the end
* Resolving a few other small issues
* Some minor config updates are needed
* For instance, we don’t need to be including an app path for func
TGs, only perf TGs
* Rte_flow testing:
* Same status as before - appears to be running fine but requires
additional review.
* Tested on Mellanox and Intel
* Remaining func testsuites:
* Qinq: Needs a review
* Ethertype: Needs a review but probably moving to 25.11
=====================================================================
Any other business
* Next Meeting Jul 9, 2025
[-- Attachment #2: Type: text/html, Size: 4063 bytes --]
reply other threads:[~2025-07-08 22:50 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=CAJvnSUAr78vbPCDnF_xav7Own8d_zgm5cK0ZuWU4+5yzLDCbcw@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).