From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>
Subject: Community CI Meeting Minutes - April 17, 2025
Date: Fri, 25 Apr 2025 10:10:48 -0400 [thread overview]
Message-ID: <CAJvnSUB-rDP66K4a5_ZRAbW6_BvEXQLTtT2BH7CXxhUZ7TqjgA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5836 bytes --]
#####################################################################
April 17, 2025
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Luca Vizzarro
4. Aaron Conole
5. Manit Mahajan
#####################################################################
Minutes
=====================================================================
General Announcements
* DPDK Summit Prague is May 8-9
* Patrick will share out his presentation to the DTS group when its ready
* Aaron has the metrics he needs for his presentation
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Intel Quickassist crypto tests: John McNamara gave us a contact for this
- Kai Ji (who is the quickassist maintainer for DPDK). UNH still needs to
pull together the performance metrics to share with Kai before we turn on
the reporting for this test.
* Environment info for reports:
* There was some discussion on Slack about what environment information
is reported alongside tests, and what can be seen from the dashboard. Some
basic info (distro, kernel, compiler version) is included on the test
report emails, and can also be found on the dashboard like:
https://lab.dpdk.org/results/dashboard/test-matrix/105/
* But, there are some improvements the lab can do, like extending the
amount of environment information included (so far Bruce suggested
including libc version) and also automatically updating the environment
info more frequently
* Manit is working on running a python script on Jenkins every 48 hours
which will collect system info for a test environment and update the
respective environment’s fields in our database
* We can also start inserting more environment info directly into the
top of the test log files which our dashboard hosts for download/view on
test results. This will be a follow up task.
* Baremetal updates:
* Cody is working on updates to our testbeds, either on a software level
or moving some NICs to new systems.
* UNH will perform a Jenkins migration in the next couple weeks which will
likely result in a few hours of lab downtime. This will be communicated
ahead of time.
* DTS:
* Dean is adding some new network cards, and has made some small
improvements to our jenkins scripting which handles starting the DTS
execution and handling the output etc. We will be able to talk about this
some at the DTS presentation at DPDK Prague.
* Patch depends-on support:
* The patchwork server series is approved and will be in the next release
* The associated git-pw patch is also merged now:
https://github.com/getpatchwork/git-pw/pull/77
* So we are on track to use this once the next patchwork patch is
released and we upgrade the dpdk.org patchwork instance
* Patrick should email Ali now to start this conversation
---------------------------------------------------------------------
Intel Lab
* Patrick will have to schedule a sync with the people that touch these
testbeds in the Summer to help them setup the DTS framework on their
systems.
---------------------------------------------------------------------
Github Actions
* None
---------------------------------------------------------------------
AWS
* They have been running their Build and Unit tests on x86 and ARM systems
for 2 weeks, and sending test reports to an external email (not the dpdk
test report mailing list). They are scheduled to begin sending the reports
to the dpdk test report mailing list this week.
---------------------------------------------------------------------
Loongarch Lab
* None
=====================================================================
DTS Improvements & Test Development
* Thomas M has provided some feedback on the rte_flow testsuite,
identifying what are the most common items and actions the rules tested
should be based on: https://inbox.dpdk.org/dev/5050697.TLnPLrj5Ze@thomas/
* Items:
* - RTE_FLOW_ITEM_TYPE_ETH
* - RTE_FLOW_ITEM_TYPE_IPV4 / RTE_FLOW_ITEM_TYPE_IPV6
* - RTE_FLOW_ITEM_TYPE_UDP
* - RTE_FLOW_ITEM_TYPE_TCP
* - RTE_FLOW_ITEM_TYPE_VLAN
* Actions:
* - RTE_FLOW_ACTION_TYPE_QUEUE
* - RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT
* - RTE_FLOW_ACTION_TYPE_RSS (Dean make sure you check which RSS
rules are validated from the RSS testsuites which are currently under
review)
* - RTE_FLOW_ACTION_TYPE_DROP
* Reviews needed:
* Shell improvements:
https://patchwork.dpdk.org/project/dpdk/list/?series=34865
* Patrick and Nick please see this series
* RSS functions:
* Partial review from Patrick. Looks pretty good so far except for
some syntax errors and we need to agree where the RSS functions should be
kept (in a dedicated file to be imported to testsuites, or just in the
testsuite class)
* Smoke tests:
* Paul will do a review
* Old patches from UNH: Various patches need to be rebased and
resubmitted. Patrick needs to mark these as rework required on Patchwork
* ICMP filtering:
* Looks good, can be merged
* Thomas submitted a patch about creating dirs on nodes
* Packet capture test suite:
*
https://patchwork.dpdk.org/project/dpdk/patch/20250331155800.449823-2-thomas.wilks@arm.com/
* Stephen has raised that dpdk-pdump is deprecated, and this testsuite
should be rewritten from dpdk-dumpcap which is its replacement
* There will be “birds of a feather” sessions at DPDK Prague for discussion
on various subjects, and it would be ideal if we can have a discussion for
DTS interested people
=====================================================================
Any other business
* Next Meeting May 1, 2025
[-- Attachment #2: Type: text/html, Size: 6719 bytes --]
reply other threads:[~2025-04-25 14:15 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=CAJvnSUB-rDP66K4a5_ZRAbW6_BvEXQLTtT2BH7CXxhUZ7TqjgA@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).