DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] Community CI Meeting Minutes
Date: Thu, 26 Aug 2021 09:33:38 -0400	[thread overview]
Message-ID: <CAOE1vsOYx0LX03okscXaHL7Yew7T6oxjjgOmKT_xccXm-0vtgQ@mail.gmail.com> (raw)

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

DPDK Community CI Meeting Minutes

August 26, 2021

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

1. Lincoln Lavoie
2. Brandon Lo
3. Owen Hilyard
4. Henry Nadeau
5. Juraj Linkeš
6. Aaron Conole
7. Michael Santana
8. Ali Alnubani
9. Ashley Weltz
10. Lijuan Tu

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

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

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

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

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

* Failure reports from UNH are now also sent to the patch submitter
(BUG-716).
* ARM SVE emulation is now running lpm_autotest and compile testing.
* Periodic ABI test for v20.11 is now enabled as part of LTS branch testing.
* Mellanox performance testing requirements updated to 1% variation.
* TRex on Mellanox systems updated to v91.
* Various fixes to DTS, including updates to fix issues in RTE flow test
case with SCAPY.
   * Work is ongoing to fix issues in other test cases
* Work on sending periodic test reports to maintainers is underway.
   * Also working on a new view for the lab dashboard to better show and
sort periodic testing runs (i.e. view by LTS release or specific
branch/repo)
* We are starting to move to a “failure by default” model
   * This means that if DTS doesn’t produce the JSON artifacts with the
testing reports, or those reports are unreadable, that we will submit a
test named “infrastructure failure”, with a warning status.
   * This is due to hard crashes we’ve seen in DTS creating situations
where having no output is possible.
   * This also triggers an internal notification within the lab, so the lab
staff can investigate the cause.

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

* Working through / for 21.11 release, ABI testing has been disabled in
Intel as well.
* For DTS CI, working to now run all test suites that are supported by the
CI environment / servers. Working to dry run some of the CI scripts
provided by Owen.  CI system for DTS is now online and reporting to
patchworks.
* For DTS CI, should authors be notified of skipped testing (i.e. CI
infrastructure doesn’t support that test suite)?  Should this be marked as
a warning in patchwork?  Agreed it should do both of these actions, notify
the author and mark the patch as warning in patchworks.
* Should DTS CI require mandatory support for the test suites being run in
CI for DPDK, to ensure those suites are not broken by a patch?  Owen will
provide the list, for Intel to confirm the coverage.
* Also working on running the DTS patches through the formatter (Python
BLACK).

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

* Update sent for OBS support, 1 comment, expecting to apply this next
week. Need to confirm the OBS scripts (build files, etc.) are correct (i.e.
meson vs make issues).
* Arm is looking to provide an application for the OVS robot and DPDK
accounts, to “call-in” to a remote lab to enable support for working in the
arm architecture.  Need to investigate what changes will be required in
Github actions definitions (i.e. yaml, etc.) to enable the application.
Details for how this integration will be set up are being worked out now.
This is likely before the end of the year, but likely not for the 21.11
release time-frame.

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

* From the DTS improvements team, the review of the initial input (word
document) has been completed.  Will create an excel document to sort the
agreed items, status / priority and next steps to present this to the
upcoming tech board, followed by bugzilla ticket creation and work
assignments.

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

* Next Meeting: September 9, 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: 5273 bytes --]

             reply	other threads:[~2021-08-26 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 13:33 Lincoln Lavoie [this message]
2021-08-26 16:05 ` Thomas Monjalon
2021-08-26 16:27   ` Lincoln Lavoie
2021-08-31 15:47     ` Thomas Monjalon
2021-09-01 12:49       ` Owen Hilyard
2021-09-07  9:23         ` Thomas Monjalon
2021-09-07  8:36 ` David Marchand
2021-09-07 12:31   ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
  -- strict thread matches above, loose matches on Subject: below --
2021-07-15 19:48 [dpdk-ci] " Lincoln Lavoie

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=CAOE1vsOYx0LX03okscXaHL7Yew7T6oxjjgOmKT_xccXm-0vtgQ@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).