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, 15 Jul 2021 15:48:52 -0400	[thread overview]
Message-ID: <CAOE1vsNQH=kvobCfSEigqB0GL2iDZb55hMnzhKvYBzxbX+HmLA@mail.gmail.com> (raw)

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

DPDK Community CI Meeting Minutes

July 15, 2021

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

1. Lincoln Lavoie
2. Brandon Lo
3. Owen Hilyard
4. David Marchand
5. Ashley Waltz
6. Lijuan Tu
7. Ali Alnubani
8. Aaron Conole
9. Juraj Linkeš

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

1. Coverity Testing
2. CI Status
3. Test Development
4. Any other business

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

===============================================================================
Coverity Testing

* The requested tool “Coverity Desktop” is not available as part of the
“Coverity Scan” that is available to open source projects.  This is
available as part of their pair product offerings.
* The “Coverity Desktop” would support a per-patch scanning, to try to
catch issues before they are merged.
* Lincoln will look into the costs required and discuss with Thomas
Monjalon about getting this recommended to the Tech Board.

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

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

* Working on infrastructure upgrades that are causing some downtime. They
are working on getting this stable again.
* Is Intel running ABI?  Running as a daily regression test.  They are
aware of the libattomic needs for ABI.

-------------------------------------------------------------------------------
Github Actions / OBS

* Michael submitted a rework of the OBS patches, and Aaron is reviewing
them, they hope to turn it on after they finish going back and forth on any
code or design changes needed.
* Aaron will look into moving Github Actions to run testing per patch over
the next couple of days.

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

* FreeBSD 13 unit testing, waiting on updates from the community to fix
issues with FreeBSD.  There may be some changes needed for what tests can
be run on FreeBSD.
* Rolled out the percentage changes required within the dashboard
* Bare metal test machines (DTS runners) are now running the same commit
version, this version includes the change to the percentage reporting.
Moving forward, all bare metal systems will run the same versions of DTS
(i.e. upgrades will roll out across all hardware).
* Broadcom 25G (performance & functional) failures investigated and put
back into production, with the new DTS.
* Intel changes (DTS upgrades) were done successfully, put back into
production.
* Mellanox & ARM systems are still offline, as the updates are being
applied for the DTS upgrades. Ali will look into this over the next couple
of days to get the right driver versions installed.
* Installed libatomic on all container images, VMs, and bare metal systems
   * Reran the patchset to get all passing ABI tests
* FreeBSD 13.0 ABI testing is failing because of disabled driver in that
OS, will disable the ABI jobs for now on this OS. David is looking into
this with the Marvell team.
* Need to investigate failures of a couple of DTS cases on the systems,
will report back to the CI list on their status.

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

* func_reentrancy_autotest, et. al. Looks like the failing unit tests are
all isolated to ARM systems, and the tests which fail appear to be random.
We should have someone from ARM investigate the systems.  In the meantime,
Aaron is converting some of these tests to use the parent/sub testsuite
framework that Ciara Power submitted.  UNH team will reach out to the ARM
teams.
* DTS Improvement
   * Discussions are progressing. Work is being tracked here:
https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit
   * Next Meeting: Jul 21, 2021
* DPDK CI Blog:
https://docs.google.com/document/d/1BmYiJK_Ndo21bgjCZYQS2HUupHpNjkXnwsu6aj8AG1U/edit#
   * Published here: https://www.dpdk.org/news/blog/

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

* Next CI Community Meeting, July 22, 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: 5734 bytes --]

             reply	other threads:[~2021-07-15 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 19:48 Lincoln Lavoie [this message]
2021-08-26 13:33 Lincoln Lavoie
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

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='CAOE1vsNQH=kvobCfSEigqB0GL2iDZb55hMnzhKvYBzxbX+HmLA@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).