DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, dts@dpdk.org
Subject: Community CI Meeting Minutes - July 11, 2024
Date: Thu, 11 Jul 2024 13:51:00 -0400	[thread overview]
Message-ID: <CAJvnSUCGM7_GB2ki6RnXQH_pz6T6wj0fZNEzQKohvG6zu7HqWQ@mail.gmail.com> (raw)

#####################################################################
July 11, 2024
Attendees
1. Patrick Robb
2. Juraj Linkeš
3. Alex Chapman
4. Tomas Durovec
5. Jeremy Spewock
6. Adam Hassick
7. Manit Mahajan
8. Dean Marx

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

=====================================================================
General Announcements
* CFP for DPDK Summit closes July 21
* There was a call with AWS people to gauge interest in DPDK testing
on their platform.
   * Their primary interest is in the functional testing
   * Performance testing is not ideal for them as their platform has a
deep tech stack which may scale differently according to deployment
conditions, so it’s hard to publish perf numbers which will hold true
across all possible deployments.

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

---------------------------------------------------------------------
UNH-IOL Community Lab
* Pending checks appear to be working fine so far:
   * Next step is deploying a watchdog which will report to the UNH
team every time a patchseries crosses the 24 hour threshold without
all its pending checks being superseded by PASS/FAIL. This watchdog
script is written and ready to deploy.
* Xueming Li (23.11 LTS maintainer) noticed that 23.11-staging branch
was not triggering a test when he amended the latest commit and force
pushed. UNH team did a little digging and found that the commits in
question were appearing on the dpdk.org git server, but not the GitHub
DPDK mirror. Our webhook for triggering LTS-staging runs is through
GitHub, so this caused the failure to trigger CI. David is helping
troubleshoot the GitHub mirror but this is not resolved yet.
* Retests v2:
   * Targeting to deploy this by Monday, July 15
   * Once this is deployed at UNH, make sure all scripts are submitted
to dpdk-ci and help other labs deploy the updates for the retest
framework (Zhoumin from Loongson has indicated interest)
* OVS:
   * There was some discussion on the mailing list about OVS compile
testing at UNH lab. This testing has been enabled, runs from the
dpdk-latest branch on OVS, and should be catching and series which
break ovs compile.

---------------------------------------------------------------------
Intel Lab
* Patrick will contact them in the future to ask about supporting the
retest framework

---------------------------------------------------------------------
Github Actions
* None

---------------------------------------------------------------------
Loongarch Lab
* None

=====================================================================
DTS Improvements & Test Development
* The MTU setting bug for mlx5 which Jeremy reported is being fixed in
this patch: https://patches.dpdk.org/project/dpdk/patch/20240708105931.1842134-1-dsosnowski@nvidia.com/
* DTS group had a call to sync a few days ago:
   * Testpmd context manager: Now split out from the scatter testsuite
and submitted as an independent testsuite. Has some reviews and was
tested at UNH.
      * Juraj Linkeš is going to take a look at this series and the
improved interactive shell output gathering series, and will follow up
with Thomas afterwards requesting a merge
   * Patrick Robbwill ping David on Slack asking about adding a
DTS-next branch which the DTS group can use for framework patches
   * UNH team is going to focus a lot of their time over the next week
to testing and reviewing the testsuites which are “ready,” and seeing
if those can make RC3.
      * Blocklist
      * Mac_filter
      * Vlan
      * Jumboframes
      * Queue_start_stop/Dynamic_queue (this is one where we will want
to add a capability for stopping queues, which can come in the next
release)
   * “Is there a list of Test Suites currently being worked on, as to
not do the same ones? I may have missed it in the last meeting.” -Alex
      * Working tracking spreadsheet:
https://docs.google.com/spreadsheets/d/1KrAS0c08x16RddzmYm2RDR93lRYxI9_owfk-9sz6iaI/edit?gid=0#gid=0
      * Should always make a ticket when starting a new testsuite:
https://bugs.dpdk.org/buglist.cgi?quicksearch=component%3Adts&list_id=8059

=====================================================================
Any other business
* The DTS calls are now rescheduled, happening at 13:00 UTC on Thursdays.
* Next Meeting: July 25, 2024

                 reply	other threads:[~2024-07-11 17:51 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=CAJvnSUCGM7_GB2ki6RnXQH_pz6T6wj0fZNEzQKohvG6zu7HqWQ@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).