DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes - February 15, 2024
Date: Thu, 15 Feb 2024 13:43:28 -0500	[thread overview]
Message-ID: <CAJvnSUAJ3Wc7o81tUCqavU2CsiKTPXiiRJniBx=-qoUDQbvNcg@mail.gmail.com> (raw)

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

February 15, 2024

#####################################################################
Attendees
1. Patrick Robb
2. Aaron Conole
3. Juraj Linkeš
4. Ali Alnubani
5. Paul Szczpanek

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

=====================================================================
General Announcements
* Per conversation at the previous CI meeting, all labs now have enabled
testing on RFC patches:
https://patchwork.dpdk.org/project/dpdk/patch/20240213114727.550209-1-vignesh.purushotham.srinivas@ericsson.com/
* We will have the next CI meeting next Thursday Feb 22, then return to the
every other week cadence.

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

---------------------------------------------------------------------
UNH-IOL Community Lab
* Hardware Refresh:
   * Intel E810:
      * Performance testing is now turned on for this NIC, with reporting
to patchwork:
https://mails.dpdk.org/archives/test-report/2024-February/578662.html
      * Still need to dry run the functional tests and bring those online
   * NVIDIA CX7:
      * Have dry run the performance testing this week, and we are not at
the expected mpps. Patrick is going to try some updates on the system and
continue sending feedback to Ali.
* Rebuilding containers for all testing which has an ipsec-mb library
dependency (fips, zuc, snow3g) due to the minimal version increasing to
1.4:
https://inbox.dpdk.org/dev/20240130142412.2047550-1-venkatx.sivaramakrishnan@intel.com/
   * Noting that there was a conversation in 2022 about integrating the ARM
fork of the ipsec-mb repo to the main Intel repo, but that has not happened
   * In writing the new dockerfile template I noticed the latest tag on the
ARM repo includes a new dependency requirement of GCC 11, which the
existing base image (debian 11) does not ship with. I’m just going to kill
2 birds with 1 stone here and add debian 12 to the dpdk-ci template engine,
and include the ZUC/Snow3G testing there
* Gcov unit test coverage:
   * We are now producing gcov code coverage reports for the DPDK unit test
fast tests
      * This runs 1x per month
      * Need to add a Community Lab Dashboard page where people can
download these
   * Should check if we can just display the html pages within the dashboard
* Zlib PMD/Compression-Perf:
   * We have begun running the compression-perf app (via DTS) for the ZLIB
PMD, and are reporting those results to patchwork:
https://git.dpdk.org/tools/dts/tree/tests/TestSuite_compressdev_zlib_pmd.py
* Per mailing list conversation, IOL is going to dry run the pipeline DTS
testsuite on our Intel 10G NICs testbed. Will report back to the mailing
list if it works “as-is”
   * Patrick needs to find an extra DAC cable for this
* Email Based Retest Framework: Adam has started work on the flag which
will indicate to labs to re-apply the patch onto the current top of branch,
and rerun testing
   * Note: If a request comes in with this flag, we will disregard the
patchwork testing context list submitted alongside it, and simply rerun all
testing (at IOL). The reason is we don’t want to, within 1 results table,
be displaying results from multiple DPDK artifacts. Users should be able to
assume all the results on their patchseries come from the same artifact.
   * Patrick Robbshould send an email out to the CI mailing list regarding
the proposed approach, and any considerations we should have while we
implement this

---------------------------------------------------------------------
Intel Lab
* No updates from John

---------------------------------------------------------------------
Github Actions
* Did migrate the robot last week on Tuesday. It was a very quick process
and there weren’t any missed patches. Everything seems to be running as
expected.
   * A subsequent migration is still needed, because the server hosting
this VM is going to be moved (again) in 3-4 weeks.

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

=====================================================================
DTS Improvements & Test Development
* Assigned bugzilla tickets and re-ranked priority values

=====================================================================
Any other business
* Next Meeting: February 22, 2024

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

                 reply	other threads:[~2024-02-15 18:43 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='CAJvnSUAJ3Wc7o81tUCqavU2CsiKTPXiiRJniBx=-qoUDQbvNcg@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=ci@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).