DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] September 9, 2021 Community CI Meeting Minutes
Date: Thu, 9 Sep 2021 12:55:21 -0400	[thread overview]
Message-ID: <CAOE1vsOYzgACAFdKxh_RVXE_rof7ZXVDm1ST0NVWg9mDtq5Rjg@mail.gmail.com> (raw)

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

September 9, 2021

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

1. Lincoln Lavoie
2. Aaron Conole
3. Juraj Linkes
4. Ashley Weltz
5. Ali Alnubani
6. Michael Santana
7. Lijuan Tu

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

1. CI Status
2. Test Development
3. Any other business

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

=====================================================================
General

* Setting up DPDK Slack Workspace, use the following link to join:
https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw

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

---------------------------------------------------------------------
UNH-IOL Community Lab

* Disabled SVE compile and unit testing due to it taking too long and
creating a backlog
* Currently investigating increased memory-related failures in ARM unit
testing
* Workarounds made in efforts to increase dashboard performance
   * There will be additional work in the future to reduce the load times
for viewing patch results (relates to API requests for each defined test
and environment and the growing number of both).
* Planning downtime for bare-metal on Monday, Sep 13, 2021 to roll out an
updated DTS version that now includes some patches submitted by UNH-IOL.
* Updated patchworks scripts, multiple updates from Ali on detecting the
repo / branch and maintainers listings.  UNH-IOL will need to update
scripts when the change is made.

---------------------------------------------------------------------
Intel Lab

* Reviewing some of the usage of python modules within DTS, notified the
authors about the issues / required fixes.  Some fixes have been made on
the local copy, pending feedback or fixes from the authors.  This is for
detecting what test suites are modified by a specific patch.  Need feedback
from Owen at UNH-IOL.
* DPDK CI is being prepared for the 21.11 testing.
* Intel lab is not currently using the dpdk-ci scripts, but is looking into
possibly aligning with dpdk-ci for these tools.

---------------------------------------------------------------------
Github Actions & OBS

* OBS patches are still in review, Aaron has some feedback he needs to push
up.
* Github Actions work is still in process on an application that can allow
access to some additional arm based resources not currently available in
github actions. Planning for the application code to be publicly available,
once it’s complete.

=====================================================================
Test Development

* DTS Improvements group was working on some input for the tech board, but
this hasn’t been ready / reviewed yet.
* Next DTS Meeting: TBD

=====================================================================
Any other business

* Next Meeting: September 23, 2021

-- 
*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: 4216 bytes --]

                 reply	other threads:[~2021-09-09 16:55 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=CAOE1vsOYzgACAFdKxh_RVXE_rof7ZXVDm1ST0NVWg9mDtq5Rjg@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).