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 - October 31, 2024
Date: Tue, 5 Nov 2024 19:56:35 -0500	[thread overview]
Message-ID: <CAJvnSUB=fKDCghWEroKpABe7DQf7cdHD+Mhe+ScnHoSnef8LBw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4126 bytes --]

#####################################################################
October 31, 2024
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Aaron Conole

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

=====================================================================
General Announcements
* Bruce Richardson sent some Patchwork requests on slack infra-issues slack
channel
   * 1. Patchwork checks should be sorted by alphabetical order
   * 2. Provide “Pending” test status for all patchwork checks
   * UNH guys should be able to work on this, and he has also offered to
help as needed
* UNH Lab SOW process:
   * Tech board is voting on work priorities this week, and a final SOW for
2025 based on this will be shared with Nathan Southern on Friday.

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

---------------------------------------------------------------------
UNH-IOL Community Lab
* Dropping old distro versions:
   * Fedora 37 and 38, Debian 11, Rhel7 have hit EOL and are dropped
   * Cody is adding in some new distros next week
* UNH had some tests failing to run over the weekend due to a broken git
dir on our Jenkins instance. All the missed tests were triggered. We are
working through the job  queue, but results have been slower than normal
this week.
* UNH has increased our DPDK Lab container runner resources by 20% to
increase our testing speed for the build and unit tests overall
* Cryptodev-perf app testing for QAT card was disabled ahead of RC1 due to
a board configuration issue, and Patrick still needs to fix and re-enable
* DPDK-CI mailing list:
   * Applied the dts tags config change patch
   * Patrick needs to provide his review tag (he has already reviewed) for
the create_series_artifact.py patch (adds devtools/meson-check)

---------------------------------------------------------------------
Intel Lab
* None

---------------------------------------------------------------------
Github Actions
* Planning on applying the cirrus-ci patches next week. Then, we need to
work on the cirrus yaml file to enable freebsd
   * Macos is also an option, and could possibly be supported as it has a
freebsd compatibility layer (not sure about this though)

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

=====================================================================
DTS Improvements & Test Development
* Prebuilt binaries patch series:
   * Merged
   * For the remote=false option, we are logging warnings about “Failed to
get remote dpdk tree path” and remote dpdk build dir, even though this is
the expected situation when remote=false. Is this the behavior we want?
* Merging testsuites:
   * VLAN suite is merged
   * Next, Patrick wants to merge mac_filter (done)
   * Also, want to merge l2fwd and blocklist (Thomas is resubmitting these
with the new testcase decorater, and we need to rerun them to ensure they
are working properly)
   * Dean is updating the dynamic_queue in order for it to leverage the
rx_queue_info dataclass provided currently in testpmd_shell
* Asyncsniffer:
   * Nick found a race condition for the asyncsniffer which affects us on
some systems with Intel NICs
   * Resolving in the short term with a sleep(500ms) or similar, but
leaving a ticket open for this to provide a better solution in the future
      * Nick published the patchseries and bug ticket yesterday
* Patrick should make a bugzilla ticket noting the current paramiko
behavior in DTS (retries when initiating the connection to nodes, and
unclean exit at end of execution).
* DTS results overview json:
   * Dean started testing this
   * Saw the testsuites values were all “UNDEFINED”
* Pydantic:
   * Please review UNH people…

=====================================================================
Any other business
* Legacy DTS: There was a submission today from a Marvell employee for the
cryptodev app and some testcases for the cn10k
* Next Meeting Nov 14, 2024

[-- Attachment #2: Type: text/html, Size: 4333 bytes --]

                 reply	other threads:[~2024-11-06  0:58 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=fKDCghWEroKpABe7DQf7cdHD+Mhe+ScnHoSnef8LBw@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).