From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org, dts@dpdk.org
Subject: Community CI Meeting Minutes - June 22, 2023
Date: Thu, 22 Jun 2023 10:33:37 -0400 [thread overview]
Message-ID: <CAJvnSUBGxep_Z8Vpcvz3B3izk15k_j2VbQj7QE0v4PPh5T+O2g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4328 bytes --]
June 22, 2023
#####################################################################
Attendees
1. Patrick Robb
2. Aaron Conole
3. Jeremy Spewock
4. Ali Alnubani
5. Adam Hassick
6. Manit Mahajan
7. Juraj Linkeš
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. DTS Improvements & Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* DPDK Userspace: Sept 12-13 in Dublin Ireland - Gibson Hotel
* Email based retesting framework
* Ali will upgrade to Patchwork 3.1 following the 23.07 release, which
includes two new category options on the /events API, cover-comment-created
and patch-comment-created. Comment content can be extracted after fetching
the event, and then processed.
* Should labs fetch events when a category is cover-comment-created
or patch-comment-created, or both?
* Fine to retest the existing dpdk tarball “as-is” as opposed to
re-applying on the latest git tree and making a new dpdk tarball
* In situations where the tree is in a bad state, being able to
re-apply on latest tree is a big improvement
* Can make applying to latest dpdk and retesting part of a v2 of
retesting framework
* There should be a way of monitoring the test results posted to patchwork
so that if there are tests missing, an alert can be sent to the lab (and
possibly others)
* This can catch email based issues and also reporting bugs from labs
* Query patchwork for patches older than 24 hours and check for all
expected test results missing
* Ali is going to create a ci mailing list project on Patchwork
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Added automatic json web token refresh functionality to our fips
acvp_tool.py. When the NIST API is serving requests unusually slowly
(because of load, or whatever reason) it is possible for your existing jwt
to expire during a single test run. By renewing the jwt as needed, this
issue is resolved
* This is in production at UNH and a patch to update the upstream is
submitted to the ci mailing list
* The first set of NIC shipments have arrived, which are the Intel E810s.
We plan to begin reporting results from these NICs after the 23.07 release.
* We have been laying the groundwork for the retesting framework by:
* Creating test groups and a jenkins script which can trigger retests of
specific tests based on patchwork contexts/labels
* Adding a reporting stage to every individual test, instead of relying
on “earlier in the ci process” monolithic report stages which wait on
completion of all individual tests before sending a single report
* Setting up script to parse comments and trigger subsets of a ci run
accordingly
* Requesting reviews on the UNH’s templated container image build system
---------------------------------------------------------------------
Intel Lab
* None
---------------------------------------------------------------------
Loongarch Lab
* None
---------------------------------------------------------------------
Github Actions
* No major news, but working with a new intern on setting up new internal
processes (like retesting)
=====================================================================
DTS Improvements & Test Development
* Jeremy has provided acks/reviews for patches on the 23.07 roadmap
* Jeremy submitted a v1 of his smoke test patch series - this is now
“complete”
* How to deal with overlap on patches between smoke tests and tg
abstraction. Use depends-on or include the same overlapping code between
both patches - went with the 2nd option.
* Some more work and a new version of tg abstraction will be getting
submitted soon
=====================================================================
Any other business
* Next meeting is Jul 6, 2023
--
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: 6435 bytes --]
reply other threads:[~2023-06-22 14:33 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=CAJvnSUBGxep_Z8Vpcvz3B3izk15k_j2VbQj7QE0v4PPh5T+O2g@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@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).