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 C322442214; Thu, 31 Aug 2023 18:06:55 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C9FA740285; Thu, 31 Aug 2023 18:06:55 +0200 (CEST) Received: from mail-oo1-f52.google.com (mail-oo1-f52.google.com [209.85.161.52]) by mails.dpdk.org (Postfix) with ESMTP id 33A9A4027B for ; Thu, 31 Aug 2023 18:06:54 +0200 (CEST) Received: by mail-oo1-f52.google.com with SMTP id 006d021491bc7-5738949f62cso594212eaf.0 for ; Thu, 31 Aug 2023 09:06:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1693498013; x=1694102813; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=B3q7O51M1lFbzIsvK/BTBpAo0Ug19aCpuJIub7q+sJ0=; b=JtQvhOefJf774hZPBwuPcx5JgfYRpj+khhZ3EaoSzBD2PmVy7Qo5+6BkLVtP9yOsQl vqBDh1T+5eNhce3+Rw+bk2fJR/EiqDz4Lo73x4Bk3PG/F4duyb2zquPU/gKRDx/2ujRX atumn3PVwa7FMzionKMvkFtCboZmu9t8oTpos= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693498013; x=1694102813; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=B3q7O51M1lFbzIsvK/BTBpAo0Ug19aCpuJIub7q+sJ0=; b=DTiJ0IYWyb7bnsQFdFUtZn2holQq4j5gHdKDixB77FWZtGUrRC/dcHp78aQV32MqFc 78k3yt3jb0RcByVX+Nj0wg1CKhaY6QIDARbwpOxfD2isEIFOMlU2i9i8Z5FeCi+lQCxB GhZealk4Gt6yKMi4ueJosuJDRNTZbdozbHzEFLdVo19wI6Kb74DaP7FfWzDDZm/Vd/UH moDE4jr0zdVuWFsOAdC5wcFvTPadYWZrR9PI3rlq0gShLUcFLiy4O8bXol3FX73fCloC jRzR1EFY9CEyHz1JQltoY190BTQi6pwkzWxi3QWS00shKt7PUwrw3E3dFYUfHRwM/v7c 15TA== X-Gm-Message-State: AOJu0Yy/tfj1WHkN3NCe3MOVdcRFPE85SZjR4VcTNsXQc2D0qyaZLJDM bGJ8d8azppoPhNgJsdd1Vh4T3SuZhyLuxVbQBcWsuyJL/pXWOY0du4E= X-Google-Smtp-Source: AGHT+IEemNgHeVk8oKrEfrltTqKDzEJKY/VR1QTl94XlBXB9wyP50QsRt5GQYuTNM8r/ii9ifHTnQYCkWHsHzXIoflQ= X-Received: by 2002:a4a:7502:0:b0:571:2644:f304 with SMTP id j2-20020a4a7502000000b005712644f304mr4798297ooc.8.1693498012332; Thu, 31 Aug 2023 09:06:52 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 31 Aug 2023 12:06:41 -0400 Message-ID: Subject: Community CI Meeting Minutes - August 31, 2023 To: ci@dpdk.org Cc: dts@dpdk.org Content-Type: multipart/alternative; boundary="00000000000075563606043a3be9" 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 --00000000000075563606043a3be9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable August 31, 2023 ##################################################################### Attendees 1. Patrick Robb 2. Adam Hassick 3. Aaron Conole 4. Bruce Richardson 5. Juraj Linke=C5=A1 6. Paul Szczepenek 7. Ali Alnubani ##################################################################### 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 * The next CI meeting will be rescheduled from September 14th to September 21st, to avoid a clash with DPDK summit travel. The following meeting on September 28th will return us to our normal cycle. * There is a gov board and tech board session on the 11th with some ci discussion in both meetings * Unit test suites: Bruce=E2=80=99s patch for dynamically building the unit= test suites has hit mainline * David=E2=80=99s patch fixing the memory leak from PCI device probing (= arm64) is still pending * V3 of patch for skipping specific tests based on an env variable is submitted * Opting to use an environment variable to skip the tests based on command line parsing concerns * Patrick should ack this =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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: * cx5 is back online * Hardware Refresh * The CX6 NIC is running with no reporting. It is testing at line rates for performance test runs with frame sizes 256-1518, but is falling below line rate for the test when run for 64B and 128B frames. * Is this due to packet overhead? * Currently this is running on a gen3.0 x8 pci slot * Ali is going to remote onto the testbed soon to take a look * CX7: backordered * 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? * Connection to host and rest of network should be blocked, and dispose of vm after each run * Intel 8970 QAT Accelerator card: * The custom patch doesn=E2=80=99t cleanly apply on the kernel after che= cking out to 5.4.0-155(currently running), so I=E2=80=99d like to just rebuild th= e kernel from 5.15 or 6.0. But, I don=E2=80=99t want to do it without ARM people aut= horizing it, so I=E2=80=99ll proceed once I have the go-ahead from them. * Juraj: ubuntu versions should be uniform across the lab (so 22.04 for all systems) * Retesting framework roadmap - UNH: * This is online, and an email explaining the process has been sent to the dev mailing list: https://inbox.dpdk.org/dev/CAC-YWqiXqBYyzPsc4UD7LbUHKha_Vb3=3DAot+dQomuRLoj= y2hvA@mail.gmail.com/ * We will add some basic instructions to the DPDK website: https://inbox.dpdk.org/web/20230831031834.9271-2-probb@iol.unh.edu/T/#u * We=E2=80=99ll also put something on the community lab dashboard about = page * TS-Factory: Using our dev testbed, Adam has attempted to run the ethdev testsuite on a few nics (MLNX cx5, Intel x710, Intel E810). We have only gotten the test suite to run on our CX5s so far. Oktet lab is communicating with us to resolve some issues we=E2=80=99ve run into and provide guidance regarding how this can be used in CI. * Adam discovered the bug that the RCF (remote control) implementation for ts-factory required that DNS returned v4 ip addresses to the test engine when initiating connections to the tester and DUT systems. Andrew at Oktet labs hotfixed this for the testing branch we are using it, and this bugfix will hit ts-factory mainline soon * New changes (as of a few days ago) to ts-factory are causing =E2=80=93= werror builds of the testsuite to fail, which has been reported to Oktet labs and they are working on this week * How to use this in a ci context? * The DPDK testsuite has approx 6000 test cases, which presently takes 9 hours to run, and none of the NICs supported by ts-factory will pass all of them. So, there is not an expectation that all tests will pass. The =E2=80=9CBublik=E2=80=9D tool used by the framework allows for comparis= on of pass/fails from the previous run to the current run, but Oktet says this output is aimed for human readability and is not designed for automation. * There is a flag for cutting down the testsuite to =E2=80=9Csanity c= heck=E2=80=9D testcases, which we could more reasonably expect to pass 100%. This would mean we could more reasonably report CI results, expecting 100% passes, and also it would mean a much shorter runtime. but my guess is this is throwing the baby out with the bathwater, as those sanity checks results won=E2=80= =99t be very valuable. * Do we need to run this periodically, as opposed to on every patch, due to the test duration? * Should we find a way to report some kind of result based on what tests pass? I don=E2=80=99t yet know if this is feasible. Or, we can simply= run it and store the human readable artifact on the dashboard at an easy to find place. * Does not compile on ARM, but we can reach out to Oktet/ARM to resolve these issues * Test engine only has to compile on a non-worker node, and that node could be x86 * Need to figure out what exactly has to be compiled on the (arm) worker node and communicate with oktet labs if there are issues * Patrick and Aaron talked about the UNH possibly doing more redundancy testing for the Intel lab. So, running some of the testsuites they=E2=80=99= re running which we aren=E2=80=99t. * It looks like Intel is reporting results again (woohoo!) * Patrick will determine the coverage gap between UNH and the Intel lab before Dublin so that he can discuss it with any interested parties in person * Last meeting Aaron asked about maintainers for next-* branches getting immediate CI runs on an =E2=80=9Con-push=E2=80=9D basis, like with the LTS-= staging branches. There is nothing preventing this except A. There needs to be a github mirror so we can use the github API (like we do with LTS-staging), and B. to Aaron=E2=80=99s point from last time, we need to agree on testrun frequency. * 2024 SOW item? --------------------------------------------------------------------- Intel Lab * They are reporting results again --------------------------------------------------------------------- Loongarch Lab * none --------------------------------------------------------------------- Github Actions * Retest framework: currently testing this internally, and will soon submit it for review. * Physical server move: downtime will occur at the end of the year or beginning of next year * Figuring out if there=E2=80=99s a way to migrate the VM to another sys= tem so that downtime is reduced. Otherwise, it will be about a week of downtime =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Paul Szczepanek will be working on DTS * Should be included in any conversation for DTS improvement group * Group met last week to discuss DTS roadmap for 23.11, and Honnappa is sending that out today * Jeremy is porting over the scatter testsuite and packet module for packet comparison/other packet related functions * Juraj - Documentation * What tools to generate the API docs? Sphinx (developed for python, is a natural choice) or Doxygen. * We need to agree on the format of the documentation * Juraj likes Google docs format (very readable) * Jeremy will review this patch * DTS roadmap * 1) Documentation * 2) TG related code (Packet manipulation and verification module, Support for TREX which require Non-packet-capture method enhancements) * 3) Scatter test suite * 4) Merge pending patches =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 September 21, 2023 --00000000000075563606043a3be9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
August 31, 2023

###################################= ##################################
Attendees
1. Patrick Robb
2. Ad= am Hassick
3. Aaron Conole
4. Bruce Richardson
5. Juraj Linke=C5= =A1
6. Paul Szczepenek
7. Ali Alnubani

#######################= ##############################################
Agenda
1. General Anno= uncements
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
=C2=A0 =C2=A0* The next CI meeting will be rescheduled from Septem= ber 14th to September 21st, to avoid a clash with DPDK summit travel. The f= ollowing meeting on September 28th will return us to our normal cycle.
= =C2=A0 =C2=A0* There is a gov board and tech board session on the 11th with= some ci discussion in both meetings
* Unit test suites: Bruce=E2=80=99s= patch for dynamically building the unit test suites has hit mainline
= =C2=A0 =C2=A0* David=E2=80=99s patch fixing the memory leak from PCI device= probing (arm64) is still pending
=C2=A0 =C2=A0* V3 of patch for skippin= g specific tests based on an env variable is submitted
=C2=A0 =C2=A0 =C2= =A0 * Opting to use an environment variable to skip the tests based on comm= and line parsing concerns
=C2=A0 =C2=A0 =C2=A0 * Patrick should ack thi= s
=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 tes= ting:
=C2=A0 =C2=A0* cx5 is back online
=C2=A0 =C2=A0* Hardware Refre= sh
=C2=A0 =C2=A0 =C2=A0 * The CX6 NIC is running with no reporting. It i= s testing at line rates for performance test runs with frame sizes 256-1518= , but is falling below line rate for the test when run for 64B and 128B fra= mes.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Is this due to packet overhead= ?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Currently this is running on a gen= 3.0 x8 pci slot
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Ali is going to remo= te onto the testbed soon to take a look
=C2=A0 =C2=A0 =C2=A0 * CX7: back= ordered
=C2=A0 =C2=A0* Running DTS within a VM as a security measure?=C2=A0 =C2=A0 =C2=A0 * Will require pci passthrough, cant be done with vir= tio
=C2=A0 =C2=A0 =C2=A0 * Does this added level of complexity justify t= he benefits?
=C2=A0 =C2=A0 =C2=A0 * Connection to host and rest of netwo= rk should be blocked, and dispose of vm after each run
* Intel 8970 QAT = Accelerator card:
=C2=A0 =C2=A0* The custom patch doesn=E2=80=99t cleanl= y apply on the kernel after checking out to 5.4.0-155(currently running), s= o I=E2=80=99d like to just rebuild the kernel from 5.15 or 6.0. But, I don= =E2=80=99t want to do it without ARM people authorizing it, so I=E2=80=99ll= proceed once I have the go-ahead from them.
=C2=A0 =C2=A0 =C2=A0 * Jura= j: ubuntu versions should be uniform across the lab (so 22.04 for all syste= ms)
* Retesting framework roadmap - UNH:
=C2=A0 =C2=A0* This is onlin= e, and an email explaining the process has been sent to the dev mailing lis= t: https://inbox.dpdk.org/dev/CAC-YWqiX= qBYyzPsc4UD7LbUHKha_Vb3=3DAot+dQomuRLojy2hvA@mail.gmail.com/
=C2=A0 = =C2=A0* We will add some basic instructions to the DPDK website: h= ttps://inbox.dpdk.org/web/20230831031834.9271-2-probb@iol.unh.edu/T/#u<= br>=C2=A0 =C2=A0* We=E2=80=99ll also put something on the community lab das= hboard about page
* TS-Factory: Using our dev testbed, Adam has attempte= d to run the ethdev testsuite on a few nics (MLNX cx5, Intel x710, Intel E8= 10). We have only gotten the test suite to run on our CX5s so far. Oktet la= b is communicating with us to resolve some issues we=E2=80=99ve run into an= d provide guidance regarding how this can be used in CI.
=C2=A0 =C2=A0*= Adam discovered the bug that the RCF (remote control) implementation for t= s-factory required that DNS returned v4 ip addresses to the test engine whe= n initiating connections to the tester and DUT systems. Andrew at Oktet lab= s hotfixed this for the testing branch we are using it, and this bugfix wil= l hit ts-factory mainline soon
=C2=A0 =C2=A0* New changes (as of a few d= ays ago) to ts-factory are causing =E2=80=93werror builds of the testsuite = to fail, which has been reported to Oktet labs and they are working on this= week
=C2=A0 =C2=A0* How to use this in a ci context?
=C2=A0 =C2=A0 = =C2=A0 * The DPDK testsuite has approx 6000 test cases, which presently tak= es 9 hours to run, and none of the NICs supported by ts-factory will pass a= ll of them. So, there is not an expectation that all tests will pass. The = =E2=80=9CBublik=E2=80=9D tool used by the framework allows for comparison o= f pass/fails from the previous run to the current run, but Oktet says this = output is aimed for human readability and is not designed for automation. <= br>=C2=A0 =C2=A0 =C2=A0 * There is a flag for cutting down the testsuite to= =E2=80=9Csanity check=E2=80=9D testcases, which we could more reasonably e= xpect to pass 100%. This would mean we could more reasonably report CI resu= lts, expecting 100% passes, and also it would mean a much shorter runtime. = but my guess is this is throwing the baby out with the bathwater, as those = sanity checks results won=E2=80=99t be very valuable.
=C2=A0 =C2=A0 =C2= =A0 * Do we need to run this periodically, as opposed to on every patch, du= e to the test duration?
=C2=A0 =C2=A0 =C2=A0 * Should we find a way to r= eport some kind of result based on what tests pass? I don=E2=80=99t yet kno= w if this is feasible. Or, we can simply run it and store the human readabl= e artifact on the dashboard at an easy to find place.
=C2=A0 =C2=A0 =C2= =A0 * Does not compile on ARM, but we can reach out to Oktet/ARM to resolve= these issues
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Test engine only has t= o compile on a non-worker node, and that node could be x86
=C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0* Need to figure out what exactly has to be compiled o= n the (arm) worker node and communicate with oktet labs if there are issues=
* Patrick and Aaron talked about the UNH possibly doing more redundancy= testing for the Intel lab. So, running some of the testsuites they=E2=80= =99re running which we aren=E2=80=99t.
=C2=A0 =C2=A0* It looks like Int= el is reporting results again (woohoo!)
=C2=A0 =C2=A0* Patrick will dete= rmine the coverage gap between UNH and the Intel lab before Dublin so that = he can discuss it with any interested parties in person
* Last meeting A= aron asked about maintainers for next-* branches getting immediate CI runs = on an =E2=80=9Con-push=E2=80=9D basis, like with the LTS-staging branches. = There is nothing preventing this except A. There needs to be a github mirro= r so we can use the github API (like we do with LTS-staging), and B. to Aar= on=E2=80=99s point from last time, we need to agree on testrun frequency. <= br>=C2=A0 =C2=A0* 2024 SOW item?
=C2=A0 =C2=A0
----------------------= -----------------------------------------------
Intel Lab
* They are = reporting results again

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

---------------= ------------------------------------------------------
Github Actions* Retest framework: currently testing this internally, and will soon submi= t it for review.
* Physical server move: downtime will occur at the end= of the year or beginning of next year
=C2=A0 =C2=A0* Figuring out if th= ere=E2=80=99s a way to migrate the VM to another system so that downtime is= reduced. Otherwise, it will be about a week of downtime

=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/presentatio= n/d/1fm8EtbzEQHrFyHoHiy0PNQz3MYY2NsQRatR_eC3SvHw/edit#slide=3Did.g260b440c6= 9d_0_331
=C2=A0 =C2=A0* Honnappa, Juraj, and Patrick
* Paul Szcze= panek will be working on DTS
=C2=A0 =C2=A0* Should be included in any co= nversation for DTS improvement group
* Group met last week to discuss DT= S roadmap for 23.11, and Honnappa is sending that out today
* Jeremy is = porting over the scatter testsuite and packet module for packet comparison/= other packet related functions
* Juraj - Documentation
=C2=A0 =C2=A0*= What tools to generate the API docs? Sphinx (developed for python, is a na= tural choice) or Doxygen.
=C2=A0 =C2=A0* We need to agree on the format = of the documentation
=C2=A0 =C2=A0 =C2=A0 * Juraj likes Google docs form= at (very readable)
=C2=A0 =C2=A0* Jeremy will review this patch
* DTS= roadmap
=C2=A0 =C2=A0* 1) =C2=A0 =C2=A0 =C2=A0 =C2=A0Documentation
= =C2=A0 =C2=A0* 2) =C2=A0 =C2=A0 =C2=A0 =C2=A0TG related code (Packet manipu= lation and verification module, Support for TREX which require Non-packet-c= apture method enhancements)
=C2=A0 =C2=A0* 3) =C2=A0 =C2=A0 =C2=A0 =C2= =A0Scatter test suite
=C2=A0 =C2=A0* 4) =C2=A0 =C2=A0 =C2=A0 =C2=A0Merge= pending patches
=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
Any other business
* Next meeting is September = 21, 2023
--00000000000075563606043a3be9--