From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2CBEA42C5E; Thu, 8 Jun 2023 16:13:23 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1938C406B5; Thu, 8 Jun 2023 16:13:23 +0200 (CEST) Received: from mail-oo1-f51.google.com (mail-oo1-f51.google.com [209.85.161.51]) by mails.dpdk.org (Postfix) with ESMTP id BD09840042 for ; Thu, 8 Jun 2023 16:13:21 +0200 (CEST) Received: by mail-oo1-f51.google.com with SMTP id 006d021491bc7-55b069a7cf4so413123eaf.3 for ; Thu, 08 Jun 2023 07:13:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1686233601; x=1688825601; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=iSW6lCK3lHqyz4CYX0P2jyDnLpXvqwgbe/6Vxolu0wI=; b=fmp1Qw2f2/89Zn1qouRxvJDzGmgUSEDcRZ2doJ1/AA0ZeXkirQskGT/gLQ7pkKuCYu UpSDgGEPjW4HK2td2OfJmsxLsDBYhe8k4AOtDKN8jkEB5qdPm7tP7gPPWSZElTlDi2Vu RzPQNKpYxnF4h/qKY5fatQfw0BX0i4pr1JrjQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686233601; x=1688825601; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=iSW6lCK3lHqyz4CYX0P2jyDnLpXvqwgbe/6Vxolu0wI=; b=X0vt4ozeCmps9LTWTLlgSAnXSs3Smiu2lXFLFp97juFxLnlGI4ay01jtAPcBBpL5oI OhaHBpNZ8JkN8+fg9ubjEw1EXUL1YylniT8PYt1Xix9cYQMoPjnbttKO4JjZgWH8NzdD MNW1TufcZR32WxH0Fl+/FT5jcC/sCTaLna2LvBsEHtaeJWz1jvEItj/39ANnR0lORSg6 DqQEDbc7t6BuWypYnuuiJguwYABBTcUoRcYH2/vi0nxFdiO76lz8y9pFIk/QjAz3cPJi 00AWMuh8XseCej3r8t5L9Uz6eQK4cyfQK5i2NLikJRN1J3mpHRL2RNa4Yq7GBbGDjPNT vang== X-Gm-Message-State: AC+VfDxlSNJlUd+wDKFbOShKrVX7kugJq1j3wyGqMooMhrT4Fkbsui3k mc2k2m2d9+Z95b/OEBA1uUCInDHic3+UidaB2KeRglOa64Z1EkrfKgE= X-Google-Smtp-Source: ACHHUZ4QbuYN2Fecss/LcXyhdyxpC6RMtPQS/t4ue1GWXJfuQw2TNmexJKwNalYkJM+BjE6S7I8ZWD7u+RLWRZSASAM= X-Received: by 2002:a4a:dec2:0:b0:558:b7e5:1dd0 with SMTP id w2-20020a4adec2000000b00558b7e51dd0mr6503476oou.3.1686233600719; Thu, 08 Jun 2023 07:13:20 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 8 Jun 2023 10:13:10 -0400 Message-ID: Subject: Community CI Meeting Minutes - June 8, 2023 To: ci@dpdk.org, dts@dpdk.org Content-Type: multipart/alternative; boundary="000000000000c7941305fd9eda6c" X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org --000000000000c7941305fd9eda6c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable June 8, 2023 ##################################################################### Attendees 1. Patrick Robb 2. Ali Alnubani 3. Juraj Linke=C5=A1 4. Lijuan Tu 5. Adam Hassick 6. Aaron Conole 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 * DPDK Userspace: Sept 12-13 in Dublin Ireland - Gibson Hotel * There is a discussion ongoing on the ci mailing list regarding setting up an email based re-testing request framework. Maintainers and submittors would be able to send an email in an agreed upon format to trigger a retest of their patch series. * Format could be a key phrase + a list of comma separated list of context to retest, so like =E2=80=9C^Recheck-request: ([a-zA-Z-],? ?)=E2=80= =9D as proposed by aaron * How do we keep track of recheck requests we=E2=80=99ve already handled= ? Message IDs? Or can we just track the patch series and cap the amount of retests allowed? * Best approach is to use patchwork instead of monitoring the mailing list * Need to avoid overloading the patchwork server with requests * Upstream patchwork has events API support for requesting comments. This may solve this problem. Ali is going to talk to Thomas about this possibility. * Agreement needed regarding how long we wait between checking for retests, how we indicate we=E2=80=99ve done this, other common protocol reg= arding our use of patchwork. * There is basically a consensus for the ^Recheck-request: ([a-zA-Z-],? ?) format for retest requests =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * The lab has moved from testing Fedora35 and 36, to Fedora37 and 38. * Ccache is not working on our fedora38 clang container, significantly slowing down reporting lag this week. We are currently investigating this issue. * We need to re-enable compile test reporting for our windows environment, which has been posting to our dashboard but not reporting to patchwork. * We had some failures yesterday since a patch breaking windows build was merged into CI since we failed to report the failure to patchwork. * Will initiate reruns after this meeting * We have observed a couple incorrect apply patchset failures in the past month. After investigating it, it appears that under some circumstances we were overwriting the output of the pw_maintainers_cli.py (guess git tree) script and applying to main incorrectly, causing failures. * Adam has submitted a v6 of the DPDK CI Container build system, having run it through a spellchecker and linter. * To be upstreamed to the dpdk-ci repo: https://git.dpdk.org/tools/dpdk-ci/ * Makefiles build dockerfiles based on templates according to a set of env variables set by the user * Uses oci manifests to utilize arm and x86 images in CI * Commits across patches which affect the same files have been squashed together * Going to take one more look at isolating cores for the Intel-40G x86 test bed at UNH. If this does not reduce the nic_single_core_perf test variance below that normal 0-5% we are seeing, we will change the agreed upon performance variance threshold for a failure to 6% and bring this test bed back online --------------------------------------------------------------------- Intel Lab * Storage is full on a system at Intel Lab which has interrupted CI. This has been resolved and more storage has been allocated for this system. * Retests have been put in * Back to normal --------------------------------------------------------------------- Loongarch Lab * none --------------------------------------------------------------------- Github Actions * Working on upgrades which will facilitate deployment of features like retest framework * New teammember brought in who is working on CI processes with Michael Santana =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Jeremy submitted RFC for DTS smoke tests and utilizing paramiko for ssh + interactive DPDK apps. * Juraj is going to be doing traffic gen abstraction work in the immediate future, and he will review the smoke tests patch when time becomes availabl= e * Juraj is going to be sharing 23.07 roadmap patches with Lijuan so she can review and provide comments =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Next meeting is June 22 --=20 Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu --000000000000c7941305fd9eda6c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
June 8, 2023

######################################= ###############################
Attendees
1. Patrick Robb
2. Ali A= lnubani
3. Juraj Linke=C5=A1
4. Lijuan Tu
5. Adam Hassick
6. Aa= ron Conole
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
* DPDK Userspace: Sept 12-13 in Du= blin Ireland - Gibson Hotel
* There is a discussion ongoing on the ci ma= iling list regarding setting up an email based re-testing request framework= . Maintainers and submittors would be able to send an email in an agreed up= on format to trigger a retest of their patch series.
=C2=A0 =C2=A0* For= mat could be a key phrase + a list of comma separated list of context to re= test, so like =E2=80=9C^Recheck-request: ([a-zA-Z-],? ?)=E2=80=9D as propos= ed by aaron
=C2=A0 =C2=A0* How do we keep track of recheck requests we= =E2=80=99ve already handled? Message IDs? Or can we just track the patch se= ries and cap the amount of retests allowed?
=C2=A0 =C2=A0* Best approach= is to use patchwork instead of monitoring the mailing list
=C2=A0 =C2= =A0* Need to avoid overloading the patchwork server with requests
=C2=A0= =C2=A0 =C2=A0 * Upstream patchwork has events API support for requesting c= omments. This may solve this problem. Ali is going to talk to Thomas about = this possibility.
=C2=A0 =C2=A0* Agreement needed regarding how long we = wait between checking for retests, how we indicate we=E2=80=99ve done this,= other common protocol regarding our use of patchwork.
=C2=A0 =C2=A0 =C2= =A0 * There is basically a consensus for the ^Recheck-request: ([a-zA-Z-],?= ?) format for retest requests

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=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
* The lab = has moved from testing Fedora35 and 36, to Fedora37 and 38.
=C2=A0 =C2= =A0* Ccache is not working on our fedora38 clang container, significantly s= lowing down reporting lag this week. We are currently investigating this is= sue.
* We need to re-enable compile test reporting for our windows envir= onment, which has been posting to our dashboard but not reporting to patchw= ork.
=C2=A0 =C2=A0* We had some failures yesterday since a patch breaki= ng windows build was merged into CI since we failed to report the failure t= o patchwork.
=C2=A0 =C2=A0* Will initiate reruns after this meeting
*= We have observed a couple incorrect apply patchset failures in the past mo= nth. After investigating it, it appears that under some circumstances we we= re overwriting the output of the pw_maintainers_cli.py (guess git tree) scr= ipt and applying to main incorrectly, causing failures.
* Adam has submi= tted a v6 of the DPDK CI Container build system, having run it through a sp= ellchecker and linter.
=C2=A0 =C2=A0* To be upstreamed to the dpdk-ci re= po: https://git.dpdk.org/to= ols/dpdk-ci/
=C2=A0 =C2=A0* Makefiles build dockerfiles based on tem= plates according to a set of env variables set by the user
=C2=A0 =C2= =A0* Uses oci manifests to utilize arm and x86 images in CI
=C2=A0 =C2= =A0* Commits across patches which affect the same files have been squashed = together
* Going to take one more look at isolating cores for the Intel-= 40G x86 test bed at UNH. If this does not reduce the nic_single_core_perf t= est variance below that normal 0-5% we are seeing, we will change the agree= d upon performance variance threshold for a failure to 6% and bring this te= st bed back online

-------------------------------------------------= --------------------
Intel Lab
* Storage is full on a system at Intel= Lab which has interrupted CI. This has been resolved and more storage has = been allocated for this system.
=C2=A0 =C2=A0* Retests have been put in<= br>=C2=A0 =C2=A0* Back to normal

-----------------------------------= ----------------------------------
Loongarch Lab
* none

------= ---------------------------------------------------------------
Github A= ctions
* Working on upgrades which will facilitate deployment of feature= s like retest framework
=C2=A0 =C2=A0* New teammember brought in who is = working on CI processes with Michael Santana
=C2=A0 =C2=A0
=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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
* Jeremy submitted RFC for DTS smoke tests and utilizin= g paramiko for ssh + interactive DPDK apps.
* Juraj is going to be doing= traffic gen abstraction work in the immediate future, and he will review t= he smoke tests patch when time becomes available
* Juraj is going to be = sharing 23.07 roadmap patches with Lijuan so she can review and provide com= ments

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DAny other business
* Next meeting is June 22

=
--

Patrick Robb

Technical Service Manage= r

UNH InterOperability Laboratory

21 = Madbury Rd, Suite 100, Durham, NH 03824

ww= w.iol.unh.edu


<= span style=3D"font-size:10pt;font-family:Arial;color:rgb(51,51,51);backgrou= nd-color:transparent;vertical-align:baseline;white-space:pre-wrap">

--000000000000c7941305fd9eda6c--