From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ci-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id C0BD042DEA;
	Thu,  6 Jul 2023 16:55:57 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id B8D6142FBC;
	Thu,  6 Jul 2023 16:55:57 +0200 (CEST)
Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com
 [209.85.161.50]) by mails.dpdk.org (Postfix) with ESMTP id 73FC641101
 for <ci@dpdk.org>; Thu,  6 Jul 2023 16:55:56 +0200 (CEST)
Received: by mail-oo1-f50.google.com with SMTP id
 006d021491bc7-56598263d1dso524338eaf.0
 for <ci@dpdk.org>; Thu, 06 Jul 2023 07:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=iol.unh.edu; s=unh-iol; t=1688655355; x=1691247355;
 h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
 :date:message-id:reply-to;
 bh=I2ftjLl/sYZFvLYQb/DujrOAb3D0jq4L70RrsFi0YdU=;
 b=SNXiZ4reWHGXVK8PJd4548j9SVy2yFjODyzDiLo4yEE7DEY0C/NiJ/XUjcJJKBMk51
 jPC8SyKWmeYLxSom06rbOfXX2y2uuGbHj1Uj0jyaiKYt5GPuoqbWRIdF+GdJq7ncdRAd
 Kek9qmBmo4MG7VDnkih0W7/Lyt+0x9mzhs0i0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1688655355; x=1691247355;
 h=to:subject:message-id:date:from:mime-version:x-gm-message-state
 :from:to:cc:subject:date:message-id:reply-to;
 bh=I2ftjLl/sYZFvLYQb/DujrOAb3D0jq4L70RrsFi0YdU=;
 b=FOrWGOvoDottllWt7dDDmNgr1UGBb/LfSSoFA46jCsPXiZbXBwwc8ocgLnkayBoQLg
 0DvyqT0lhqvD+Lcdv7SogY1qkEHhB82ALj6/DOg6neuAKd8PPpyvcHtalD/iRXzXCk3B
 XzX80pQZocb7b5SmicbMmuyHOMdhniOrUOtjsr1Z0tnfy8LM60tX3vAc+ebJOpiKBhTg
 L70SbO5h5A4mxuylGNm1SZEh4w3sk8mWHTImr4eyf48VYlg4ast0d3m53vs9ZNMw5K1n
 iHrGUd+MhFHBeAkEg2bh71038pcJuZVJzcjOiFRFv59fkHu4onaMWRlD5imwqU81X8yd
 C1oA==
X-Gm-Message-State: ABy/qLZPTaLcX8R9rvbmJ6p81frBEJ3U18V/NCv5QyTiDZbA3FFqhUgc
 x0pDkpDP8QQnp/51YYPQc/UeVX9xK2IFe1vI9Uqd/EW703+FDOCND7Y=
X-Google-Smtp-Source: APBJJlF6cQq0EUgi+dfYW2eUIwa6dqDgCNoVp7Q7mPMWXgM9DMFPONuxge9Jl5IKtABJcU93gF/6ZPxSSOpFHoHGLnw=
X-Received: by 2002:a4a:45ce:0:b0:565:a620:4efa with SMTP id
 y197-20020a4a45ce000000b00565a6204efamr1523621ooa.6.1688655355585; Thu, 06
 Jul 2023 07:55:55 -0700 (PDT)
MIME-Version: 1.0
From: Patrick Robb <probb@iol.unh.edu>
Date: Thu, 6 Jul 2023 10:55:44 -0400
Message-ID: <CAJvnSUBXCdi1nXag0cH=u+CUTQP+tf5d0BLOM3EjS=4u5iwpYQ@mail.gmail.com>
Subject: Community CI Meeting Minutes - July 6, 2023
To: ci@dpdk.org, dts@dpdk.org
Content-Type: multipart/alternative; boundary="0000000000009e388d05ffd2b616"
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
 <mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
 <mailto:ci-request@dpdk.org?subject=subscribe>
Errors-To: ci-bounces@dpdk.org

--0000000000009e388d05ffd2b616
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

July 6, 2023

#####################################################################
Attendees
1. Patrick Robb
2. Manit Mahajan
3. Lincoln Lavoie
4. Aaron Conole
5. Ali Alnubani
6. Juraj Linkes
7. Jeremy Spewock

#####################################################################
Agenda
1. General Announcements
2. CI Status
3. DTS Improvements & Test Development
4. Any other business

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
General Announcements
* Ali has created a dpdk-ci project on dpdk patchwork, allowing for better
tracking of incoming patch series

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CI Status

---------------------------------------------------------------------
UNH-IOL Community Lab
* On Monday a patch was merged into main which changes behavior relating to
the libnuma dependency for compiling dpdk. This tripped up our apply
patchset + compile pipeline, and as a consequence we began publishing build
error results for unrelated incoming patch series. We have made the libnuma
dependency change needed to return to normal CI, and we are working now to
backfill with reruns for all affected patch series.
   * Unfortunately this coincided with USA=E2=80=99s independence day, whic=
h is why
we couldn=E2=80=99t address this =E2=80=9Csame day=E2=80=9D
   *
https://git.dpdk.org/dpdk/commit/?id=3D5afed6966da072e7f569871d86421e70c232=
6601
   * No results were published to patchwork from IOL due to it failing at
the apply patchset+compile stage failing. So, there may not have been
awareness of this matter from the developer/maintainer side.
      * This also makes submitters think they are still waiting on results
to come in
   * After applying patchset in our script, we do a sanity compile before
passing the patch series to our CI. This might be causing more harm than
good by preventing results from being published.
   * This connects to the conversation from the previous meeting regarding
setting up an automated process for checking that all expected results have
been published to patchwork
      * Should this be handled from the lab side, or the patchwork project
side?
      * IOL could send up an initial report (unh-iol-testing), which can
display a failure if a build error occurs, and can report a pass once we
see all (ci wide) results are up.
* Jeremy=E2=80=99s patch series for refreshing NIST json web tokens has bee=
n
approved and merged into upstream dpdk-ci
* We are continuing to lay the groundwork for correctly re-triggering
testing pipelines per email based retesting requests
* Adam is exploring the tsfactory testing framework by setting it up on our
development servers. This is a tech board request which may allow for
expanded ethdev related testing.
* We are internally testing usage of gcov/lcov to produce unit test
coverage reports. Initially this would just be tracking coverage related to
the =E2=80=9Cfast tests=E2=80=9D meson unit test suite, but could possibly =
be expanded
later. Discussions regarding the most appropriate use of the tool are
ongoing, but we could run this regularly and publish results if desired.
Or, they may just serve as a helpful internal tool and reference point.
   * This can be regularly published to the dashboard (1x week/month or
something)
   * Can we have dedicated runs which cover all built in unit test suites?
   * Can we expand this to DTS, etc?
   * Gcov can =E2=80=9Cself-aggregate=E2=80=9D by adding to an existing fil=
e
   * There are tools which can read these and show not only how much code
is being covered, but also which code
      * Lab will look into cobertura
* We=E2=80=99ve added a system to our CI dedicated for running containerize=
d
report/saving type jobs, to avoid situations where heavy testing load means
all of our container runners are =E2=80=9Cbusy=E2=80=9D and results which a=
re ready to be
reported have to wait in queue for executor slots
   * This is mostly a quality of life change reducing time from patch
submission to reporting, but it also helps prevent situations where our CI
=E2=80=9Clocks up=E2=80=9D
* NIC hardware refresh:
   * 2 Intel E810s are in, DAC cabling has arrived, this NIC will be
installed in the to be donated Intel server
   * 1 of the 2 mlnx cx6 cards are in, the other is backordered
   * No news from Ericcson about the embedded snow board
   * Additional E810 has arrived to act as a traffic generator for Marvell,
still waiting on them to ship their hardware
   * Everything else is ordered

---------------------------------------------------------------------
Intel Lab
* None

---------------------------------------------------------------------
Loongarch Lab
* None

---------------------------------------------------------------------
Github Actions
* Aaron has some code which will scan comments for a reported context
   * Right now it scans on the open patches for comments - he is working on
refactoring this for the events API
   * Should there be a universal script for this which all labs use, or
should every lab write their own script?
      * Aaron is using https://github.com/ovsrobot/pw-ci currently for
other patchwork based projects. It may be possible for our script to be
integrated here, preventing some work overlap between labs.
* Also writing the script for kicking off the required retest according to
the result of calling the events API

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
DTS Improvements & Test Development
* Some 23.07 DTS roadmap patches are still not merged.
   * Jeremy has been testing patches on UNH=E2=80=99s development test bed =
servers,
and is adding =E2=80=9Ctested-bys=E2=80=9D for those series. That work will=
 continue today.
* Release has been postponed a few days, we should have time until July 17t=
h
* Juraj is sending his final patch submission soon, and has some comments
for Jeremy=E2=80=99s patches which he can send in today
   * A sync is needed regarding how to manage overlap between patches
* We will schedule a call between DTS folks to discuss final steps before
the 23.07 release

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Any other business
* Aaron still waiting for confirmation that the talk regarding making the
community lab a gating mechanism for patches
   * Also will just update the community regarding some of the challenges
the lab faces
* Next meeting is Jul 20, 2023

--0000000000009e388d05ffd2b616
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">July 6, 2023<br><br>######################################=
###############################<br>Attendees<br>1. Patrick Robb<br>2. Manit=
 Mahajan<br>3. Lincoln Lavoie<br>4. Aaron Conole<br>5. Ali Alnubani<br>6. J=
uraj Linkes<br>7. Jeremy Spewock<br><br>###################################=
##################################<br>Agenda<br>1. General Announcements<br=
>2. CI Status<br>3. DTS Improvements &amp; Test Development<br>4. Any other=
 business<br><br>##########################################################=
###########<br>Minutes<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>General Announcements<br>* Ali has created a dpdk-ci projec=
t on dpdk patchwork, allowing for better tracking of incoming patch series<=
br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>CI St=
atus<br><br>---------------------------------------------------------------=
------<br>UNH-IOL Community Lab<br>* On Monday a patch was merged into main=
 which changes behavior relating to the libnuma dependency for compiling dp=
dk. This tripped up our apply patchset + compile pipeline, and as a consequ=
ence we began publishing build error results for unrelated incoming patch s=
eries. We have made the libnuma dependency change needed to return to norma=
l CI, and we are working now to backfill with reruns for all affected patch=
 series.<br>=C2=A0 =C2=A0* Unfortunately this coincided with USA=E2=80=99s =
independence day, which is why we couldn=E2=80=99t address this =E2=80=9Csa=
me day=E2=80=9D <br>=C2=A0 =C2=A0* <a href=3D"https://git.dpdk.org/dpdk/com=
mit/?id=3D5afed6966da072e7f569871d86421e70c2326601">https://git.dpdk.org/dp=
dk/commit/?id=3D5afed6966da072e7f569871d86421e70c2326601</a><br>=C2=A0 =C2=
=A0* No results were published to patchwork from IOL due to it failing at t=
he apply patchset+compile stage failing. So, there may not have been awaren=
ess of this matter from the developer/maintainer side.<br>=C2=A0 =C2=A0 =C2=
=A0 * This also makes submitters think they are still waiting on results to=
 come in<br>=C2=A0 =C2=A0* After applying patchset in our script, we do a s=
anity compile before passing the patch series to our CI. This might be caus=
ing more harm than good by preventing results from being published.<br>=C2=
=A0 =C2=A0* This connects to the conversation from the previous meeting reg=
arding setting up an automated process for checking that all expected resul=
ts have been published to patchwork<br>=C2=A0 =C2=A0 =C2=A0 * Should this b=
e handled from the lab side, or the patchwork project side?<br>=C2=A0 =C2=
=A0 =C2=A0 * IOL could send up an initial report (unh-iol-testing), which c=
an display a failure if a build error occurs, and can report a pass once we=
 see all (ci wide) results are up.<br>* Jeremy=E2=80=99s patch series for r=
efreshing NIST json web tokens has been approved and merged into upstream d=
pdk-ci<br>* We are continuing to lay the groundwork for correctly re-trigge=
ring testing pipelines per email based retesting requests<br>* Adam is expl=
oring the tsfactory testing framework by setting it up on our development s=
ervers. This is a tech board request which may allow for expanded ethdev re=
lated testing. <br>* We are internally testing usage of gcov/lcov to produc=
e unit test coverage reports. Initially this would just be tracking coverag=
e related to the =E2=80=9Cfast tests=E2=80=9D meson unit test suite, but co=
uld possibly be expanded later. Discussions regarding the most appropriate =
use of the tool are ongoing, but we could run this regularly and publish re=
sults if desired. Or, they may just serve as a helpful internal tool and re=
ference point. <br>=C2=A0 =C2=A0* This can be regularly published to the da=
shboard (1x week/month or something)<br>=C2=A0 =C2=A0* Can we have dedicate=
d runs which cover all built in unit test suites?<br>=C2=A0 =C2=A0* Can we =
expand this to DTS, etc?<br>=C2=A0 =C2=A0* Gcov can =E2=80=9Cself-aggregate=
=E2=80=9D by adding to an existing file<br>=C2=A0 =C2=A0* There are tools w=
hich can read these and show not only how much code is being covered, but a=
lso which code<br>=C2=A0 =C2=A0 =C2=A0 * Lab will look into cobertura<br>* =
We=E2=80=99ve added a system to our CI dedicated for running containerized =
report/saving type jobs, to avoid situations where heavy testing load means=
 all of our container runners are =E2=80=9Cbusy=E2=80=9D and results which =
are ready to be reported have to wait in queue for executor slots<br>=C2=A0=
 =C2=A0* This is mostly a quality of life change reducing time from patch s=
ubmission to reporting, but it also helps prevent situations where our CI =
=E2=80=9Clocks up=E2=80=9D<br>* NIC hardware refresh: <br>=C2=A0 =C2=A0* 2 =
Intel E810s are in, DAC cabling has arrived, this NIC will be installed in =
the to be donated Intel server<br>=C2=A0 =C2=A0* 1 of the 2 mlnx cx6 cards =
are in, the other is backordered<br>=C2=A0 =C2=A0* No news from Ericcson ab=
out the embedded snow board<br>=C2=A0 =C2=A0* Additional E810 has arrived t=
o act as a traffic generator for Marvell, still waiting on them to ship the=
ir hardware<br>=C2=A0 =C2=A0* Everything else is ordered<br>=C2=A0 =C2=A0<b=
r>---------------------------------------------------------------------<br>=
Intel Lab<br>* None<br><br>------------------------------------------------=
---------------------<br>Loongarch Lab<br>* None<br><br>-------------------=
--------------------------------------------------<br>Github Actions<br>* A=
aron has some code which will scan comments for a reported context<br>=C2=
=A0 =C2=A0* Right now it scans on the open patches for comments - he is wor=
king on refactoring this for the events API<br>=C2=A0 =C2=A0* Should there =
be a universal script for this which all labs use, or should every lab writ=
e their own script?<br>=C2=A0 =C2=A0 =C2=A0 * Aaron is using <a href=3D"htt=
ps://github.com/ovsrobot/pw-ci">https://github.com/ovsrobot/pw-ci</a> curre=
ntly for other patchwork based projects. It may be possible for our script =
to be integrated here, preventing some work overlap between labs. <br>* Als=
o writing the script for kicking off the required retest according to the r=
esult of calling the events API<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>DTS Improvements &amp; Test Development<br>* Some =
23.07 DTS roadmap patches are still not merged. <br>=C2=A0 =C2=A0* Jeremy h=
as been testing patches on UNH=E2=80=99s development test bed servers, and =
is adding =E2=80=9Ctested-bys=E2=80=9D for those series. That work will con=
tinue today. <br>* Release has been postponed a few days, we should have ti=
me until July 17th<br>* Juraj is sending his final patch submission soon, a=
nd has some comments for Jeremy=E2=80=99s patches which he can send in toda=
y<br>=C2=A0 =C2=A0* A sync is needed regarding how to manage overlap betwee=
n patches<br>* We will schedule a call between DTS folks to discuss final s=
teps before the 23.07 release<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>Any other business<br>* Aaron still waiting for co=
nfirmation that the talk regarding making the community lab a gating mechan=
ism for patches<br>=C2=A0 =C2=A0* Also will just update the community regar=
ding some of the challenges the lab faces<br>* Next meeting is Jul 20, 2023=
</div>

--0000000000009e388d05ffd2b616--