From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: DPDK Community CI Minutes - July 21, 2022
Date: Thu, 21 Jul 2022 10:40:54 -0400 [thread overview]
Message-ID: <CAOE1vsNkSHk1f0GKAP2P9wGyPAEsDqYeKwpSP-gkP9LH2xPHhA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3793 bytes --]
###########################################################
Attendees
1. Lincoln Lavoie
2. Juraj Linkeš
3. Maksym Vynnyk
4. Ali Alnubani
5. Michael Santana
6. David Marchand
7. Jeremy Spewock
###########################################################
Agenda
1. General Announcements
2. CI Status
3. Test Development
4. Any other business
###########################################################
Minutes
===========================================================
General Announcements
* Userspace Summit, September 6-8, 2022,
https://events.linuxfoundation.org/dpdk-userspace-summit/, call for papers
closes on July 22. September 6 will be the DPDK Hackathon, Tech Board
Meeting, and Reception.
===========================================================
CI Status
-----------------------------------------------------------
UNH-IOL Community Lab
* ABI testing on DPDK main has been disabled, while things move towards the
22.11 LTS release. ABI testing will be “rebased” on that release once it’s
complete
* Patch submitted for OpenSSL test case, to prevent IPsec cases from
running when unintended.
*
https://patchwork.dpdk.org/project/dpdk/patch/20220712141701.27797-1-jspewock@iol.unh.edu/
* https://bugs.dpdk.org/show_bug.cgi?id=1045
* The patch is recommended for back-porting, so the LTS branches can run
these unit tests.
* Both Broadcom and Mellanox systems should be back online. Need to
confirm Broadcom results are reporting up to patchworks, Jenkins jobs are
running.
* Monday will have some short downtime of the dashboard to roll out some
small changes / improvements to internal infrastructure. This will not
impact ongoing / running testing.
* Nearly complete with adding the test coverage map to the dashboard.
Populates based on tests run during a specified interval (i.e. prior 2
weeks).
* Lab would like to plan for testing downtime in August, to allow for
installing Jenkins updates. This will also deploy the changes to to only
keep past 8 months of results artifacts (approximately 2 releases). This
reduces the time required for Jenkins updates, when it has to inject and
update old data (i.e. schema changes).
* During the same down-time, the lab will also be replacing some physical
infrastructure (UPSes and switches).
-----------------------------------------------------------
Intel Lab
* No updates / attendance
-----------------------------------------------------------
Github Actions
* Minor issue with the Github runner, was offline for a day. There is some
planned downtime this weekend for maintenance, shutdown Friday, brought
back up on Monday.
* Team is still planning for an update / upgrade for the runner, this
should have minimal downtime and the team will confirm when it happens.
===========================================================
Test Development
* Need feedback on the patch from the DPDK community on the first DTS
changes / submission,
https://patchwork.dpdk.org/project/dpdk/list/?series=23961
* Discussions around the library used for ssh control of the tester / dut
and the underlying library.
* Another discussion around concurrency, and what can be run in parallel
and how will that be accomplished.
* Looking into reworking how the traffic generators are implemented /
abstracted in the DTS code. Owen submitted an example direction that is
being reviewed / discussed.
===========================================================
Any other business
* Next Meeting: August 4, 2022
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 4964 bytes --]
reply other threads:[~2022-07-21 14:41 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=CAOE1vsNkSHk1f0GKAP2P9wGyPAEsDqYeKwpSP-gkP9LH2xPHhA@mail.gmail.com \
--to=lylavoie@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).