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 165EDA00C2 for ; Thu, 8 Dec 2022 16:57:16 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E52A340E28; Thu, 8 Dec 2022 16:57:15 +0100 (CET) Received: from mail-oa1-f48.google.com (mail-oa1-f48.google.com [209.85.160.48]) by mails.dpdk.org (Postfix) with ESMTP id E17DB40A7E for ; Thu, 8 Dec 2022 16:57:13 +0100 (CET) Received: by mail-oa1-f48.google.com with SMTP id 586e51a60fabf-1443a16b71cso2255570fac.13 for ; Thu, 08 Dec 2022 07:57:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=IjmeVzxoAhZDHpXLjXZOrQpNglgn5EcuHQGRE3HgUNo=; b=B1A3pMC/pwyo5TblmxXvYxv/u1Cox/tGCB7+H+2dbtl7xM+7Ji2CL2gZyF/+FiA85Z sU6K/bEbQgKoEHH3GY+w2f4aQpNxRjXSOMSdNzbTjPzITJQnbJqX2wuR041mfX8qMAPA gzC5C5E00wnPHveA4fSFqYWrpwIDiuMdDu+Do= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=IjmeVzxoAhZDHpXLjXZOrQpNglgn5EcuHQGRE3HgUNo=; b=007yf+AZb7i2C8bjdUSll6e6VWxdZMOXcok1onXPGWZWjYT9EQT1P1d60ePDuyMTRo FgeRXGGssiHbKeNNtXCCjgDfUTi4c2c83PggEhy6wXec1FeoIMv2OuznboyOWoa7pArr /ExQRTMdgwOWCQlJ543onFPHegOKLfeHKBf7dmWrG0zSEJDT5mb/HgNjmnV/ZflX1+ZE TOdgFglgJcfy+xt2wOl8aROox8f5QAJqNrJO+Whv41BjydjMdg8lhO4os0ZlxOLAqaAC WwpcC2T7aec9YSpYrsZAp8ZWrzr2w4lY/5o7ZiVNc5LKKYdXl2ay0ZaKL9p67KfknYym HJ/g== X-Gm-Message-State: ANoB5pkv9zOW9Tp1/pnvHy7/79Zr2so8U+lBRKwtgw4SkdwWtKhoMyvM M94I12j13kJqVbyjuDHEvk4cJ6HZU14MO4R1Lt7XG7YwOYAIY+1XtN8= X-Google-Smtp-Source: AA0mqf7iEB8LMEwhucPriWv2W3Sio/8vKpAYnJpRo433ZeRLJ0G/wn+CbV6YbmncIjlm0f2p5JS9doGDJhVXl9ILBIw= X-Received: by 2002:a05:6871:4802:b0:141:b187:158f with SMTP id qc2-20020a056871480200b00141b187158fmr44378098oab.247.1670515032545; Thu, 08 Dec 2022 07:57:12 -0800 (PST) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 8 Dec 2022 10:57:01 -0500 Message-ID: Subject: Community CI Meeting Minutes - December 8th, 2022 To: ci@dpdk.org Content-Type: multipart/alternative; boundary="0000000000001b70c105ef531706" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --0000000000001b70c105ef531706 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable December 8, 2022 ##################################################################### Attendees 1. Patrick Robb 2. Min Zhao 3. Lincoln Lavoie 4. Juraj Linke=C5=A1 5. Ali Alnubani 6. Aaron Conole 7. Jeremy Spewock 8. Lijuan Tu ##################################################################### 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 * 2022 Retrospective: https://docs.google.com/document/d/1DMf-Lkl6QIJbe7wtX1aJz6mdHiITZjuUbufyCZB= g-WY/edit * 2023 Lab priorities: https://docs.google.com/spreadsheets/d/1GW0hTbEXjA0ZmDLrQRhXwPFu8X-o8qH1sMB= Tdg2bDyE/edit#gid=3D0 * LTS 22.11.1 released * Should the 22.11 tag be updated to point to 22.11.1, right now, it effectively points to 22.11.0? This would involve changing git history, which the maintainers never do. Thomas followed up via email stating that this was off the table. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Periodic testing is now added for 22.11 LTS release, and for the 22.11-staging branch of dpdk-stable. * David notified us on Slack about an issue with the incorrect commit urls being assigned to our tarballs acquired for dpdk-stable testing. This does not affect testing accuracy, but it is annoying, and I will apply the fix for that later today. * Environment created for ZUC & Snow3G PMD unit tests, which have been manually run successfully. The team is currently building a Jenkins pipeline to get this online. * After touching base with Dell support again about the RAID controller on the Ampere test bed, they determined a replacement was in order and are shipping on to the lab. * Owen has brought Kmod testing against linux-next to production * ABI testing rollout pending updates to lab code / scripts or resolution of the conversation about 22.11 tag. --------------------------------------------------------------------- Intel Lab * The maintainer for next-broadcom may be inactive - a bugfix applied to main two months ago was not pulled to next-broadcom, and Lijuan is unable to get a response from the maintainer on this. * What does the timeline look like for 19.11 EOL? There will be one more (final) release next week. * Intel CI Lab has some ideas for long term support testing - in the old days only the latest revision of a branch would be tested - Intel is considering also permanently testing the very first version of a release (like 22.11.0). Some customers may always stick to using the initial version of a release. --------------------------------------------------------------------- Loongarch Lab * There may be some problems with the test-report mail server. Some emails from Loongson with test results have been blocked. * Ali: =E2=80=9CIt seems that the emails have been getting rejected by t= he mailing list's server since Tuesday because loongson's mail server was detected in a data set for addresses associated with spam. I just double checked and it seems the address was removed from the spam list. Can you please try to resend?=E2=80=9D --------------------------------------------------------------------- Github Actions * Aaron has merged a change from David which adds some series dependencies support to GHA-Robot * Aaron having a meeting with Rashid Khan regarding how the tech board can get responses back to UNH regarding the SOW =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Work continues on the hello world test case * Further discussion needed regarding how DTS handles failures - currently whenever a failure occurs anywhere in the process it is caught and recorded, then DTS moves on. It is a problem when it=E2=80=99s unclear whet= her a failure is caused by DTS or DPDK - DTS team wants to make the feedback from failures more clear, and obviously just make DTS more stable in general. * Owen is interested in adding exit code to DTS for additional feedback on failures. Juraj will follow up with Owen to figure out how exactly this can be best implemented for CI testing purposes. * How can we deal with multiple failures at the same time? Can there be a hierarchy of exit codes? * One idea is to place a higher priority on on failures from DPDK as opposed to a DTS failure =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 meetings: December 22, January 5, sticking to the normal schedule. * December 28th DTS meeting will be canceled as Honappa is on sabbatical until January 3rd. * Tech board meeting is on January 14th for UNH feedback --=20 Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu --0000000000001b70c105ef531706 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
December 8, 2022

##################################= ###################################
Attendees

1. Patrick Robb
= 2. Min Zhao
3. Lincoln Lavoie
4. Juraj Linke=C5=A1
5. Ali Alnubani=
6. Aaron Conole
7. Jeremy Spewock
8. Lijuan Tu

###########= ##########################################################
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

= * 2022 Retrospective: https://docs.google.com/documen= t/d/1DMf-Lkl6QIJbe7wtX1aJz6mdHiITZjuUbufyCZBg-WY/edit
* 2023 Lab pr= iorities: https://docs.google.com/spreads= heets/d/1GW0hTbEXjA0ZmDLrQRhXwPFu8X-o8qH1sMBTdg2bDyE/edit#gid=3D0
*= LTS 22.11.1 released
=C2=A0 =C2=A0* Should the 22.11 tag be updated to = point to 22.11.1, right now, it effectively points to 22.11.0? This would i= nvolve changing git history, which the maintainers never do. Thomas followe= d up via email stating that this was off the table.

=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Commun= ity Lab

* Periodic testing is now added for 22.11 LTS release, and f= or the 22.11-staging branch of dpdk-stable.
=C2=A0 =C2=A0* David notifie= d us on Slack about an issue with the incorrect commit urls being assigned = to our tarballs acquired for dpdk-stable testing. This does not affect test= ing accuracy, but it is annoying, and I will apply the fix for that later t= oday.
* Environment created for ZUC & Snow3G PMD unit tests, which = have been manually run successfully. The team is currently building a Jenki= ns pipeline to get this online.
* After touching base with Dell support = again about the RAID controller on the Ampere test bed, they determined a r= eplacement was in order and are shipping on to the lab.
* Owen has broug= ht Kmod testing against linux-next to production
* ABI testing rollout p= ending updates to lab code / scripts or resolution of the conversation abou= t 22.11 tag.

-------------------------------------------------------= --------------
Intel Lab

* The maintainer for next-broadcom may b= e inactive - a bugfix applied to main two months ago was not pulled to next= -broadcom, and Lijuan is unable to get a response from the maintainer on th= is.
* What does the timeline look like for 19.11 EOL? There will be one = more (final) release next week.
* Intel CI Lab has some ideas for long t= erm support testing - in the old days only the latest revision of a branch = would be tested - Intel is considering also permanently testing the very fi= rst version of a release (like 22.11.0). Some customers may always stick to= using the initial version of a release.

--------------------------= -------------------------------------------
Loongarch Lab

* There= may be some problems with the test-report mail server. Some emails from Lo= ongson with test results have been blocked.
=C2=A0 =C2=A0* Ali: =E2=80= =9CIt seems that the emails have been getting rejected by the mailing list&= #39;s server since Tuesday because loongson's mail server was detected = in a data set for addresses associated with spam. I just double checked and= it seems the address was removed from the spam list. Can you please try to= resend?=E2=80=9D
=C2=A0 =C2=A0
-------------------------------------= --------------------------------
Github Actions

* Aaron has merge= d a change from David which adds some series dependencies support to GHA-Ro= bot
* Aaron having a meeting with Rashid Khan regarding how the tech boa= rd can get responses back to UNH regarding the SOW

=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 D= evelopment

* Work continues on the hello world test case
* Furthe= r discussion needed regarding how DTS handles failures - currently whenever= a failure occurs anywhere in the process it is caught and recorded, then D= TS moves on. It is a problem when it=E2=80=99s unclear whether a failure is= caused by DTS or DPDK - DTS team wants to make the feedback from failures = more clear, and obviously just make DTS more stable in general.
=C2=A0 = =C2=A0* Owen is interested in adding exit code to DTS for additional feedba= ck on failures. Juraj will follow up with Owen to figure out how exactly th= is can be best implemented for CI testing purposes.
=C2=A0 =C2=A0 =C2=A0= * How can we deal with multiple failures at the same time? Can there be a = hierarchy of exit codes?
=C2=A0 =C2=A0* One idea is to place a higher pr= iority on on failures from DPDK as opposed to a DTS failure

=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 meetings: December 22, January 5, sticking to the normal sched= ule.
* December 28th DTS meeting will be canceled as Honappa is on sabba= tical until January 3rd.
* Tech board meeting is on January 14th for UNH= feedback

--

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

<= span style=3D"font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-= color:transparent;vertical-align:baseline;white-space:pre-wrap">21 Madbury = Rd, Suite 100, Durham, NH 03824

www.iol.un= h.edu


=

--0000000000001b70c105ef531706--