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 16, 2023
Date: Thu, 16 Feb 2023 10:31:27 -0500	[thread overview]
Message-ID: <CAJvnSUDY3+XzZ2APw9DYKRiEQNaA7+7NjuFft79j+gTsizi6oQ@mail.gmail.com> (raw)

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

February 16, 2023

#####################################################################
Attendees
1. Patrick Robb
2. Lincoln Lavoie
3. Adam Hassick
4. Aaron Conole
5. Juraj Linkeš
6. Lijuan Tu
7. Michael Santana
8. Ali Alnubani

#####################################################################
Agenda
1. General Announcements
2. CI Status
3. DTS Improvements & Test Development
4. Any other business

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

=====================================================================
General Announcements
* None

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

---------------------------------------------------------------------
UNH-IOL Community Lab
* On Monday we sent an email to the dev mailing list regarding the issues
with the FIPS sample app documentation, which has not generated a
conversation as of this meeting. What we can do currently is extend our
FIPS CI testing to include all currently functional test vectors. As stated
in our email, if there is interest from any community members for update
documentation, we are happy to write up our setup process.
* We have completed the work to upgrade from the dpdk-ci repo’s
guess_git_tree.py to the more up to date pw_maintainers_cli.py script,
which should reduce the amount of patches being applied to incorrect
branches. The work for this was completed yesterday, and we will roll this
out on our CI today.
* ZUC/SNOW3G autotests are deployed, running on debian 11.
* Our updated container building process for multi-arch support is now
functional, which unblocks some goals such as upstreaming the container
building system and re-enabling ccache, which will significantly improve
our testing speed.
* We are beginning work on extending test coverage to 32 bit for x86 and
ARM. We will need to limit this to one distro per CPU architecture due to
testing capacity.
   * For ARM, testing will be done bare metal on the Altra server
   * For x86, we are currently investigating system requirements
* Unit_test_mbuf failures seen this morning on the Arm Altra server are
most likely the result of a bad merge made yesterday, but we will
investigate this morning to verify there is no infra failure

---------------------------------------------------------------------
Intel Lab
* Extending its test coverage on container test beds. This will be online
in approximately a month.
* Should documentation patches be ignored? These should not affect CI
results.
   * Spell check CI testing could provide some value
   * With multiple doc patches all being applied to the current git state
of dpdk main, it may make sense to run CI to ensure there are no conflicts
which bring on apply errors.
   * This decision can be determined by the tech board or may be able to be
resolved via the CI mailing list

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

---------------------------------------------------------------------
Github Actions
* Working on events API patch - waiting for review
* Small outage this past weekend - CI was shutdown and was brought back
online on Monday

=====================================================================
DTS Improvements & Test Development
* refer to DTS WG minutes

=====================================================================
Any other business
* Next meeting is March 2nd

-- 

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu

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

                 reply	other threads:[~2023-02-16 15:31 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=CAJvnSUDY3+XzZ2APw9DYKRiEQNaA7+7NjuFft79j+gTsizi6oQ@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).