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 May 20, 2021
Date: Thu, 20 May 2021 10:24:46 -0400	[thread overview]
Message-ID: <CAOE1vsN5W_N1EVQOysM7A-J=Vb_B_EQiqCbQ0Ym7GuD0B7vrBw@mail.gmail.com> (raw)

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

May 20, 2021

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

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

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

1. Performance Metric Change to Percentage
2. CI Lab Status
3. Test Development
4. Any Other Business

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

=====================================================================
Performance Metric Change to Percentage

* Patch series is still pending merge:
https://patchwork.dpdk.org/project/dts/list/?series=15990
* Blocked by: https://bugs.dpdk.org/show_bug.cgi?id=670

=====================================================================
CI Lab Status

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

* Unit testing has been rolled out to all container runners (all Linux
distros).
** Investigating failures and rerunning if failures are real
* The apply patch job sends out warnings when patches fail to apply.
* Starting to investigate putting Fedora 34 into pipeline to expand
coverage.
Bug https://bugs.dpdk.org/show_bug.cgi?id=679
** Intel lab currently has Fedora 33 in production/testing on their side.
Should we still try and expand onto Fedora 33 as well?
** Lab will bring both Fedora 33 and Fedora 34 online for testing /
reporting.
* Rolling out FreeBSD 13.0 for compile, unit, and ABI testing.  Will then
retire FreeBSD 11.2.
* Currently looking into 40G Intel machine issues.
** Emails have been sent out to Intel to schedule a time to the debug this
issues.
* Dynamic Config DTS test case is failing, due to roll back of patch
dealing with white space trimming in expected output.  DTS team is working
on this currently, should we disable the test case for the time being?
https://bugs.dpdk.org/show_bug.cgi?id=639 Agreed to disable this until the
DTS patch is readded.
* Need to confirm the compiler version used and if possible add GCC11 and
CLANG12.

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

   * Intel lab had a critical issue, missed submitting patches / results.
Root cause has been identified as a lab power failure / cycle.  Has been
fixed and results should be reporting in again.
   * Upgraded Fedora 33 to Fedora 34.

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

   * Found an issue within OBS on the meson build.  Proposing to fork the
build scripts to a dedicated repo for the OBS systems, so this can be
directly maintained. This is currently blocking re-enabling OBS reporting.
   * Travis has been removed from the CI resources for the project, it can
still be used by individual developers.
   * Arm is working on a solution to provide aarch64 resources via a
private running for Github actions.

=====================================================================
CI / Test Development

---------------------------------------------------------------------
DTS Improvement

* Discussions are progressing. Work is being tracked here:
https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit
* Next Meeting: Wednesday, May 26, 2021, at 1pm UTC

---------------------------------------------------------------------
Developer Retesting Request

* https://mails.dpdk.org/archives/ci/2021-May/001189.html
* Seeking feedback on the “command syntax.”  Still need to implement the
tracking / mechanics for things like patches and message ID tracking.

---------------------------------------------------------------------
Community Lab Objectives

* Q1 Update to the techboard:
https://docs.google.com/document/d/1v0VKtZdsMXg35WNDawdsnqj5J4Xl9Egu_4180ukKD2o
* Status tracking is also being partly carried out in Bugzilla.  Epics have
been created for each major objective. This will span 2021, do not expect
them to be closed quickly. Updates posted to each objective will track
story completion, etc.  This is a compromise of how to easily track the
long term objectives.

---------------------------------------------------------------------
Open Requests (outside of planned objectives)

* Add meson syntax check testing (https://bugs.dpdk.org/show_bug.cgi?id=696)
* Will leave this open for now for folks to give feedback on.
* Alpine Linux - I believe there was a request for this that went by, but I
can’t track it down.  This is a sanity check, am I misremembering, or is
this a real request?
** Request was from Thomas.  Alpine Linux is now being supported as of the
latest DPDK release.

=====================================================================
Any Other Business

   * Coverity Recheck (for rc4) - Brandon will look into running this
today, so the fixes can be verified.
   * Next CI meeting: June 2, 2021, 1pm UTC

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

                 reply	other threads:[~2021-05-20 14:24 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='CAOE1vsN5W_N1EVQOysM7A-J=Vb_B_EQiqCbQ0Ym7GuD0B7vrBw@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).