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 3AA4043092; Thu, 17 Aug 2023 16:20:08 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 10E93410FD; Thu, 17 Aug 2023 16:20:08 +0200 (CEST) Received: from mail-oo1-f47.google.com (mail-oo1-f47.google.com [209.85.161.47]) by mails.dpdk.org (Postfix) with ESMTP id 0B3E740685 for ; Thu, 17 Aug 2023 16:20:06 +0200 (CEST) Received: by mail-oo1-f47.google.com with SMTP id 006d021491bc7-56d455462c2so5355431eaf.2 for ; Thu, 17 Aug 2023 07:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1692282005; x=1692886805; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=jRG5vQ2ApnAt4asd1KGrrP4t6zmv73wz3aQMssASI8U=; b=PqFbNOQpQ83xi72JXvXHHlo/GdGeWZZtNnirbY8qn9Ydw76KMClbDKMA8+9tjIF0K1 Pvgov2MwWwbuR6iPU2recu8IJ5L2dR8ImGeWxO1PgfEn2KGxDJPun5F9l2KnxzvFRNXj 0JPoRGzg2oPyBuOp9TKQ76gonff8xNZxqqe5I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692282005; x=1692886805; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=jRG5vQ2ApnAt4asd1KGrrP4t6zmv73wz3aQMssASI8U=; b=floWDYxg+kcbJBnFL5pDVUuN9fcnsiqZbzYkvAoHX6BVvJDnmZzJV2vfY9ZXzSEK7d 99lC8ky/jvLYMWBqf4HDnBQE3alAJAyUs5AntBr7zdkpo6jSJKA//SD+ubZowdUnMluD btrY4/3Mmq+JykXlyXvc/+VZffK3DuXNz5IT9zLCV7akUNJkQCbFanoK/UJO2b/Vh5q6 gqlhW+tVRnz+t6Xar8njzygi7JzekqjpO2Lo38xUOvZmPiIlUlRvWeBzeHinom4KSHBt 0uF7idQC3zsdRTeQPINsYnQp1pLNc8DOJKH+03cZ/9G3hNtYYRD12R5s8m8ZXV6D7DC/ ohWA== X-Gm-Message-State: AOJu0YyNs5WoO+3DgzLrwYLSe4W6VC04lifFx195jHK7S+rYWk8yM93s aiACdzfhWNgssjpFfvOZR4S4jleWBBJ/li+wv4UKnfcaDwfJ+NuN9wLlTA== X-Google-Smtp-Source: AGHT+IHSsba5aSTEBYTEy7aPcoBet/fcgyQ27Vh0BM1hOBkOS57be7qswy3kjD5vwdZK/IzM4NFAxRM4dMICBnwADY8= X-Received: by 2002:a4a:91db:0:b0:56c:d297:164c with SMTP id e27-20020a4a91db000000b0056cd297164cmr4618130ooh.4.1692282005214; Thu, 17 Aug 2023 07:20:05 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 17 Aug 2023 10:19:54 -0400 Message-ID: Subject: Community CI Meeting Minutes - August 17, 2023 To: ci@dpdk.org Cc: dts@dpdk.org Content-Type: multipart/alternative; boundary="000000000000c7f01306031f1bc8" 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 --000000000000c7f01306031f1bc8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable August 17, 2023 ##################################################################### Attendees 1. Patrick Robb 2. Bruce Richardson 3. Honnappa Nagarahalli 4. Aaron Conole 5. David Marchand 6. Manit Mahajan 7. Lincoln Lavoie ##################################################################### 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 Summit is Sept 12-13 * Should we hold the scheduled Sept 14th ci meeting? Which ci meeting regulars will be at the summit? Aaron and Patrick can=E2=80=99t make it, so= let=E2=80=99s cancel this one. * Will suggest an off normal schedule meeting to replace this * Patchwork v3: * Bruce reported incorrect series titles and missing cover letters for some newer patchseries * Don=E2=80=99t CC the ci mailing list with dpdk patches, as it may get = diverted to the ci project on patchwork. * A temporary workaround is to cc just relevant people in the ci community * Aaron is supposed to have admin permissions for the ci project on pathwork, but he needs to ping Ali about this * Unit test suites: Bruce Richardson is working on a patch which eliminates the old approach of setting the DPDK unit testuites from /app/test/meson.build, and instead dynamically builds the lists based on build configuration * This raised one issue with UNH CI, which is that we are filtering out the eal_flags_file_prefix_autotest on our ARM containers, and this will no longer be possible following Bruce=E2=80=99s rework. Bruce has suggested implementing meson functionality allowing for disabling specific tests, which is a better version of how we filter currently. * Testlogs for the failure are now shared with David who is going to try and help * David has reproduced and has seen a leak when there is 1 (and only 1) device * UNH will send lspci output from the VMs which host the containers * ARM vms are on KVM, so that might be a reason * Bruce pushed a new patch where you can set an env variable of tests to be skipped * This is better in that the tests show up as skipped instead of just not showing up at all - in this way it is clear to people looking at the logs that the test was not run, but usually is run for this testsuite * For 32 bit aarch testing, which cannot run via meson test and is dependent on the dpdk-test binary path, we will have to coordinate the merge of this patchseries with Bruce so we can modify our script, or Bruce can put a symlink connecting the old path to the new * Cross compile a version of meson to run on that? Honnappa does not think this is needed, but he is going to talk to arm folks about it. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Mellanox perf testing: * The Mellanox DUT is upgraded to 22.04 and is running perf testing, but with no reporting until Mellanox people assess the new results. So far, results appear consistent with the performance seen when the DUT was on 18.04, and with an older version of the MLNX OFED driver. * Patrick will send a report to Ali today with the results from the previous 24 hours * Hardware Refresh * The CX6 NIC is installed. Ali created a TREX config for this nic. Patrick will complete the remaining setup for perf testing. That will require a patch to DTS adding NIC info. CX7 is in the same boat. Ali shared an example from when the cx5 was added, which I will use as a reference: b6b0a575d34f ("tests/nic_single_core_perf: add support for Mellanox's nics"= ) * CX7: The SKU we ordered was discontinued, so our order has been canceled. We put in another order for a different model:MCX713106AC-CEAT * Running DTS within a VM as a security measure? * Will require pci passthrough, cant be done with virtio * Does this added level of complexity justify the benefits? * Intel 8970 QAT Accelerator card: * We still need to rebuild the kernel with the patch Ruifeng shared: https://lkml.org/lkml/2022/6/17/328 * Are there security issues or instability introduced by building the custom kernel and not changing it? * There may be an official PPA we can use with the latest official kerne= l * It should be in kernel 6.0 and newer, so it may be as simple as upgrading to the latest kernel * Retesting framework roadmap - UNH: * 1. Database migrations - done * Storing retest request relations to patchseries tarballs, and the retest datetimes, to be used as parameters for future comment requests * Will limit retest requests to x per patchseries tarball (two seems reasonable, but open to a group decision) * Limit to 1 at first * 2. Script for parsing comments for api calls to pw, contexts/labels, producing list, writing json file. - done. * This is not UNH specific and we can upstream this to the dpdk-ci repo if there=E2=80=99s interest from other labs * 3. Write jenkinsfile script for requesting comments and triggering testing pipelines according to retest requests - in progress: * What is an acceptable frequency for us to run this (which may involve many patchwork API calls) * 4. Contact community with the rules and format * Reporting: UNH rolled out =E2=80=9Ctail reporting=E2=80=9D which moves re= porting from result aggregating reporting stages at the end of our CI process, to reporting from the individual jobs which run testing. This should decrease our time to delivery for reporting, and increase our reliability, as it essentially moves us to one source of truth for reporting. * TS-Factory: We are running this on a Dev server, but need some help with setting the config files for the DPDK PMD testsuite. Adam has emailed Konstantin from Oktet Labs for clarification on this. * Consider test capacity * If Intel lab is downsizing, UNH may need to reassess our goal of adding a framework for other labs to submit results and artifacts to the UNH dashboard, since that was an Intel lab request. * Aaron is interested in maintainers getting their own branch that maintainers can push to to get test results * Similar to LTS-staging* branches * What policies would have to be set regarding how maintainers use this ability? --------------------------------------------------------------------- Intel Lab * No reports since August 12th --------------------------------------------------------------------- Loongarch Lab * none --------------------------------------------------------------------- Github Actions * Robot=E2=80=99s poller will be offline for some time in sept-october due = to systems being physically moved * The poller is run in a VM - if this can be migrated, downtime may be a day or less, but it=E2=80=99s unclear whether we can * Retesting framework: work on this is ongoing, and will be sent to the ci mailing list * Going to be re-assessing some APIs on pw and GHA, and reverting old workaround for polling via GHA =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * DTS presentation (work in progress): https://docs.google.com/presentation/d/1fm8EtbzEQHrFyHoHiy0PNQz3MYY2NsQRatR= _eC3SvHw/edit#slide=3Did.g260b440c69d_0_331 * Honnappa, Juraj, and Patrick * Jeremy submitted an RFC for porting over the Scatter Testsuite * 9AM eastern next week we will have a meeting about the DTS roadmap =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 August 31, 2023 --000000000000c7f01306031f1bc8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
August 17, 2023

###################################= ##################################
Attendees
1. Patrick Robb
2. Br= uce Richardson
3. Honnappa Nagarahalli
4. Aaron Conole
5. David Ma= rchand
6. Manit Mahajan
7. Lincoln Lavoie

####################= #################################################
Agenda
1. General A= nnouncements
2. CI Status
3. DTS Improvements & Test Development<= br>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 Summit is Se= pt 12-13
=C2=A0 =C2=A0* Should we hold the scheduled Sept 14th ci meetin= g? Which ci meeting regulars will be at the summit? Aaron and Patrick can= =E2=80=99t make it, so let=E2=80=99s cancel this one.
=C2=A0 =C2=A0 =C2= =A0 * Will suggest an off normal schedule meeting to replace this
* Patc= hwork v3:
=C2=A0 =C2=A0* Bruce reported incorrect series titles and mis= sing cover letters for some newer patchseries
=C2=A0 =C2=A0* Don=E2=80= =99t CC the ci mailing list with dpdk patches, as it may get diverted to th= e ci project on patchwork.
=C2=A0 =C2=A0 =C2=A0 * A temporary workaroun= d is to cc just relevant people in the ci community
=C2=A0 =C2=A0 =C2=A0= * Aaron is supposed to have admin permissions for the ci project on pathwo= rk, but he needs to ping Ali about this
* Unit test suites: Bruce Richar= dson is working on a patch which eliminates the old approach of setting the= DPDK unit testuites from /app/test/meson.build, and instead dynamically bu= ilds the lists based on build configuration
=C2=A0 =C2=A0* This raised o= ne issue with UNH CI, which is that we are filtering out the eal_flags_file= _prefix_autotest on our ARM containers, and this will no longer be possible= following Bruce=E2=80=99s rework. Bruce has suggested implementing meson f= unctionality allowing for disabling specific tests, which is a better versi= on of how we filter currently.
=C2=A0 =C2=A0 =C2=A0 * Testlogs for the f= ailure are now shared with David who is going to try and help
=C2=A0 =C2= =A0 =C2=A0 * David has reproduced and has seen a leak when there is 1 (and = only 1) device
=C2=A0 =C2=A0 =C2=A0 * UNH will send lspci output from th= e VMs which host the containers
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* ARM = vms are on KVM, so that might be a reason
=C2=A0 =C2=A0* Bruce pushed a = new patch where you can set an env variable of tests to be skipped
=C2= =A0 =C2=A0 =C2=A0 * This is better in that the tests show up as skipped ins= tead of just not showing up at all - in this way it is clear to people look= ing at the logs that the test was not run, but usually is run for this test= suite
=C2=A0 =C2=A0* For 32 bit aarch testing, which cannot run via meso= n test and is dependent on the dpdk-test binary path, we will have to coord= inate the merge of this patchseries with Bruce so we can modify our script,= or Bruce can put a symlink connecting the old path to the new
=C2=A0 = =C2=A0 =C2=A0 * Cross compile a version of meson to run on that? Honnappa d= oes not think this is needed, but he is going to talk to arm folks about it= . =C2=A0
=C2=A0 =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
CI Status

---------------------------------= ------------------------------------
UNH-IOL Community Lab
* Mellanox= perf testing:
=C2=A0 =C2=A0* The Mellanox DUT is upgraded to 22.04 and = is running perf testing, but with no reporting until Mellanox people assess= the new results. So far, results appear consistent with the performance se= en when the DUT was on 18.04, and with an older version of the MLNX OFED dr= iver.
=C2=A0 =C2=A0 =C2=A0 * Patrick will send a report to Ali today wit= h the results from the previous 24 hours
=C2=A0 =C2=A0* Hardware Refresh=
=C2=A0 =C2=A0 =C2=A0 * The CX6 NIC is installed. Ali created a TREX con= fig for this nic. Patrick will complete the remaining setup for perf testin= g. That will require a patch to DTS adding NIC info. CX7 is in the same boa= t. Ali shared an example from when the cx5 was added, which I will use as a= reference: b6b0a575d34f ("tests/nic_single_core_perf: add support for= Mellanox's nics")
=C2=A0 =C2=A0 =C2=A0 * CX7: The SKU we order= ed was discontinued, so our order has been canceled. We put in another orde= r for a different model:MCX713106AC-CEAT
=C2=A0 =C2=A0* Running DTS wit= hin a VM as a security measure?
=C2=A0 =C2=A0 =C2=A0 * Will require pci = passthrough, cant be done with virtio
=C2=A0 =C2=A0 =C2=A0 * Does this a= dded level of complexity justify the benefits?
* Intel 8970 QAT Accelera= tor card:
=C2=A0 =C2=A0* We still need to rebuild the kernel with the pa= tch Ruifeng shared: https:/= /lkml.org/lkml/2022/6/17/328
=C2=A0 =C2=A0* Are there security issue= s or instability introduced by building the custom kernel and not changing = it?
=C2=A0 =C2=A0* There may be an official PPA we can use with the late= st official kernel
=C2=A0 =C2=A0 =C2=A0 * It should be in kernel 6.0 and= newer, so it may be as simple as upgrading to the latest kernel
* Retes= ting framework roadmap - UNH:
=C2=A0 =C2=A0* 1. Database migrations - do= ne
=C2=A0 =C2=A0 =C2=A0 * Storing retest request relations to patchserie= s tarballs, and the retest datetimes, to be used as parameters for future c= omment requests
=C2=A0 =C2=A0 =C2=A0 * Will limit retest requests to x p= er patchseries tarball (two seems reasonable, but open to a group decision)=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Limit to 1 at first
=C2=A0 =C2= =A0* 2. Script for parsing comments for api calls to pw, contexts/labels, p= roducing list, writing json file. - done.
=C2=A0 =C2=A0 =C2=A0 * This i= s not UNH specific and we can upstream this to the dpdk-ci repo if there=E2= =80=99s interest from other labs
=C2=A0 =C2=A0* 3. Write jenkinsfile scr= ipt for requesting comments and triggering testing pipelines according to r= etest requests - in progress:
=C2=A0 =C2=A0 =C2=A0 * What is an acceptab= le frequency for us to run this (which may involve many patchwork API calls= )
=C2=A0 =C2=A0* 4. Contact community with the rules and format
* Rep= orting: UNH rolled out =E2=80=9Ctail reporting=E2=80=9D which moves reporti= ng from result aggregating reporting stages at the end of our CI process, t= o reporting from the individual jobs which run testing. This should decreas= e our time to delivery for reporting, and increase our reliability, as it e= ssentially moves us to one source of truth for reporting.
* TS-Factory: = We are running this on a Dev server, but need some help with setting the co= nfig files for the DPDK PMD testsuite. Adam has emailed Konstantin from Okt= et Labs for clarification on this.
=C2=A0 =C2=A0* Consider test capacit= y
* If Intel lab is downsizing, UNH may need to reassess our goal of add= ing a framework for other labs to submit results and artifacts to the UNH d= ashboard, since that was an Intel lab request.
* Aaron is interested in = maintainers getting their own branch that maintainers can push to to get te= st results
=C2=A0 =C2=A0* Similar to LTS-staging* branches
=C2=A0 =C2= =A0* What policies would have to be set regarding how maintainers use this = ability?
=C2=A0 =C2=A0
----------------------------------------------= -----------------------
Intel Lab
* No reports since August 12th
<= br>---------------------------------------------------------------------Loongarch Lab
* none

-------------------------------------------= --------------------------
Github Actions
* Robot=E2=80=99s poller wi= ll be offline for some time in sept-october due to systems being physically= moved
=C2=A0 =C2=A0* The poller is run in a VM - if this can be migrate= d, downtime may be a day or less, but it=E2=80=99s unclear whether we can* Retesting framework: work on this is ongoing, and will be sent to the c= i mailing list
* Going to be re-assessing some APIs on pw and GHA, and r= everting old workaround for polling via GHA

=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Developmen= t
* DTS presentation (work in progress): https://docs.google.com/presentation/d/1fm8EtbzEQ= HrFyHoHiy0PNQz3MYY2NsQRatR_eC3SvHw/edit#slide=3Did.g260b440c69d_0_331=C2=A0 =C2=A0* Honnappa, Juraj, and Patrick
* Jeremy submitted an RFC = for porting over the Scatter Testsuite
* 9AM eastern next week we will h= ave a meeting about the DTS roadmap

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Augu= st 31, 2023
--000000000000c7f01306031f1bc8--