DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minutes - January 19, 2023
Date: Thu, 19 Jan 2023 10:34:39 -0500	[thread overview]
Message-ID: <CAJvnSUDjDG8t=VyxKczR3nhO0osQ7ssfiY8G1ye4JS01c6CC3Q@mail.gmail.com> (raw)

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

January 19, 2023

#####################################################################
Attendees

1. Patrick Robb
2. Owen Hilyard
3. Ali Alnubani
4. Lincoln Lavoie
5. Michael Santana
6. Juraj Linkeš
7. Aaron
8. Michael Santana
9. Honnappa Nagarahalli
10. Adam Hassick

#####################################################################
Agenda

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

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

=====================================================================
General Announcements

* Governing board approved the SOW for 2023.
* UNH Lab member Owen Hilyard will be departing the lab on February 10th.
We thank him for his major contributions and wish him the best in his
future endeavors. We are working with Owen and the entire team to make sure
lab operations and support are uninterrupted after his departure. It’s
never easy to replace talented and hardworking team members, but we remain
committed to the project and will conduct interviews in the next days/weeks
to make sure we are able to bring another employee on board. Good luck Owen
and thank you!

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

---------------------------------------------------------------------
UNH-IOL Community Lab
* FIPS testing: We have written pipeline jobs which acquire vectors from
the ACVP API, and validate them with the cryptodev validation sample
application. The final step is adding a stage which aggregates the results
of the output .rsp files, and reports one single result to our dashboard
and Patchwork. We aim to bring this online on Monday.
   * Currently we are running this just an ubuntu container, but our
pipelines are written to allow us to easily expand to other distros if/when
needed
* Arm Ampere Altra: We did set the remaining baselines for this system, so
it is now reporting functional and performance testing across all branches
for Intel-40G. We are exploring ways to expand coverage to other NICS on
this test bed.
* We will be physically moving the servers which make up the lab in the
near future - this will result in some downtime which will be scheduled and
emailed out to the CI mailing list. All “missed” patch series will be
queued up and tested once we’re back online.
* Two ThunderX2 Arm servers have been installed in our new DPDK server
rack, which will be used as dedicated systems for unit testing. The
advantage of this is that we will be able to run unit testing on a
different system from those which run DTS.
   * These will host VMs which mirror the x86 testing process
   * Modifications to our container registry are being completed which will
allow us to maintain multi-arch images and generically run testing across
arm and x86
   * Aarch32 cross compile -> unit test: the lab needs to find a solution
to run 32 bit testing across x86 and arm without emulation. One idea for
arm is to try using thunderx1 systems - need to check if they support
aarch32.
   * Another approach is to utilize the altra, but run the testing serially
as opposed to in parallel
* IPsec: need to limit this testing to latest LTS and new patch series, and
build a dedicated image on our registry

---------------------------------------------------------------------
Intel Lab
* There may be some intel downtime due to Chinese New Year

---------------------------------------------------------------------
Loongarch Lab
* N/A

---------------------------------------------------------------------
Github Actions
* Patchwork scripts being updated - they are currently querying patchwork
by dates as opposed to events API, the latter being the preferred approach.
* Currently resolving complications on their jenkins instance due to
failures which have occurred recently

=====================================================================
DTS Improvements & Test Development
* Honappa leading a separate meeting with his minutes

=====================================================================
Any other business
* Next meeting is February 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: 6442 bytes --]

                 reply	other threads:[~2023-01-19 15:34 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='CAJvnSUDjDG8t=VyxKczR3nhO0osQ7ssfiY8G1ye4JS01c6CC3Q@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).