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 8CCBBA0547 for ; Mon, 21 Jun 2021 14:00:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6586041158; Mon, 21 Jun 2021 14:00:46 +0200 (CEST) Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) by mails.dpdk.org (Postfix) with ESMTP id 4089F40040 for ; Mon, 21 Jun 2021 14:00:45 +0200 (CEST) Received: by mail-oi1-f179.google.com with SMTP id q10so19584540oij.5 for ; Mon, 21 Jun 2021 05:00:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ACUE4nutgKqKoM5mSakRvsfwwMqVsGbrXtTbVZ4qcoE=; b=cKDTs1k7AdRi/1ATaDdWKQ7HZvPURzPEAQmZcC1SxEuv8zwNVxLGsg/6/FMigvvi2s mjijhNCAL0NwhPiWKTuVAV+7NzalnWfYFoJ3qmfWtFg56par/PZbRlsEBjIz2kZMCoWV 6h1bVeDLWWPlJwtB6q7CaZW3aUaBrniycy33E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ACUE4nutgKqKoM5mSakRvsfwwMqVsGbrXtTbVZ4qcoE=; b=ls2FnF1DhB67HJlx6783gD5hdFTc+tObWqgVkfnWeZSHN3dkI9ES6/O833xYKFxUfp 3sy9r7cftu5vv97wKCfUAm02nR2ELrvoh549bOzTyf5Ub6xtZsWuyKfktOAGPWAiFlAL AC0esJp2jAO4LEw4pBzDK2eGz82W9RAMwAYwETIjw4zaQ+wVGRuFYveXxhM5qN+mN4Oc 12lpyc29zRz8945aH+zmFKnNB0LP4LSvzmQ/oyaMLQrSf05G24lHZzBm2aP02wb/qZDu bvGfvN3Q1hLzYCiX6XVyTSSHEfOXy6L3cz09yADtop2x1q4qo2wjX0A02lve262B8Or4 2FWA== X-Gm-Message-State: AOAM530wei8EjnJg6h2Txtnmy8ezDpLpqGLuo2MtU5oeuu25iVthYaFZ k22C6KFH8schh3KyPchNPIoHh5x+vyvatYzG753lxw== X-Google-Smtp-Source: ABdhPJw0Rp6l8zlv3g5gFzGshytfRmJMfKdzQOgdmnEqONy/6BSMYOQKQYLKyUPVXzklWCALtBDKIG0rWdDNMQjK2Ns= X-Received: by 2002:aca:53ca:: with SMTP id h193mr23321982oib.69.1624276842987; Mon, 21 Jun 2021 05:00:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Owen Hilyard Date: Mon, 21 Jun 2021 08:00:07 -0400 Message-ID: To: "Chen, Zhaoyan" Cc: Lincoln Lavoie , "ci@dpdk.org" , "Lin, Xueqin" Content-Type: multipart/alternative; boundary="0000000000003e5b8f05c5456cc0" Subject: Re: [dpdk-ci] June 17 Community CI Meeting Minutes 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 Sender: "ci" --0000000000003e5b8f05c5456cc0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Zhaoyan, Here are the patches I've submitted: http://patches.dpdk.org/project/dpdk/patch/20210616195724.366103-1-ohilyard= @iol.unh.edu/ http://patches.dpdk.org/project/dpdk/patch/20210616181833.356159-1-ohilyard= @iol.unh.edu/ http://patches.dpdk.org/project/dpdk/patch/20210616180724.355217-1-ohilyard= @iol.unh.edu/ http://patches.dpdk.org/project/dpdk/patch/20210616162453.349614-1-ohilyard= @iol.unh.edu/ David: http://patches.dpdk.org/project/dpdk/patch/20210616065257.16044-1-david.mar= chand@redhat.com/ "[v2] lib/rte_rib6: fix stack buffer overflow" will be getting a v3 once priority work in our CI environment is completed. Most of these are fairly minor patches, with the exception of that one. I'll look into testing with this patch once we don't see any more leaks when running the unit tests, but that may take a while. Should this patch help mitigate some of the memory allocation problems we've seen in the unit tests when ASAN is enabled? Owen On Fri, Jun 18, 2021 at 4:17 AM Chen, Zhaoyan wrote: > Great Lincoln. > > > > Could you kindly share the patch links? > > > > /Zhaoyan > > > > *From: *Lincoln Lavoie > *Date: *Friday, June 18, 2021 at 09:55 > *To: *"Chen, Zhaoyan" > *Cc: *"ci@dpdk.org" , "Lin, Xueqin" , > Owen Hilyard > *Subject: *Re: [dpdk-ci] June 17 Community CI Meeting Minutes > > > > Hi Zhaoyan, > > > > Owen from our team has been leading the efforts on getting ASAN running o= n > (under, with) DPDK. He's got a couple of patches submitted fixing some > smaller issues he's seen. I think David Marchand also had some patches > started to fix some of the issues as well. > > > > Cheers, > Lincoln > > > > On Thu, Jun 17, 2021 at 8:39 PM Chen, Zhaoyan > wrote: > > Hi, Lincoln, > > > > For * ASAN deployment, what kind of tests are you going to deploy? > > > > We have a patch for enable ASAN for DPDK. I don=E2=80=99t know if is it h= elpful.. > > > http://patches.dpdk.org/project/dpdk/patch/20210615081205.101071-1-zhihon= gx.peng@intel.com/ > > > > Thanks > > > > /Zhaoyan > > > > *From: *ci on behalf of Lincoln Lavoie < > lylavoie@iol.unh.edu> > *Date: *Thursday, June 17, 2021 at 23:48 > *To: *"ci@dpdk.org" > *Subject: *[dpdk-ci] June 17 Community CI Meeting Minutes > > > > June 17, 2021 > > ##################################################################### > Attendees > > 1. Lincoln Lavoie > 2. Brandon Lo > 3. Owen Hilyard > 4. Aaron Conole > 5. Ali Alnubani > 6. Juraj Linke=C5=A1 > 7. Lijuan Tu > 8. Ashley Weltz > 9. Thomas Monjalon > 10. Michael Santana > 11. David Marchand > > ##################################################################### > Agenda > > 1. Performance Metric Change to Percentage > 2. Coverity Testing > 3. CI Lab Status > 4. Test Development > 5. 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 > Performance Metric Change to Percentage > > * Patch series is still pending merge: > https://patchwork.dpdk.org/project/dts/list/?series=3D15990 > * Blocked by: https://bugs.dpdk.org/show_bug.cgi?id=3D670 > * Blocks any upgrade to the latest DTS versions, which depend on the > latest TRex. > * A work around could be to skip testing specific frame sizes that cause > that issue. Ali will confirm internally and reply back to the lab on this > way forward. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Coverity Testing > > * https://bugs.dpdk.org/show_bug.cgi?id=3D719 > * Need to investigate if the lab can set up a way to desktop analysis, > which would run local to the systems. Request is to run the test per > patch, to check for additional issues being introduced by the patch. Onl= y > reports new defects. > * > https://community.synopsys.com/s/topic/0TO34000000LJdaGAG/coverity-deskto= p-analysis > I think this is not an article (just Q&A), you might have to check the > documentation in your local installation > * Need to verify the requirements for running the tool, and if it require= d > a paid account, etc. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Lab Status > > --------------------------------------------------------------------- > UNH-IOL Community Lab > > * Currently looking into 40G Intel machine issues. > * Stats checks disabled due to the requirement for VM images for the > test suite in newer DTS versions > * MTU update test suite disabled due to issue of unknown origin causin= g > packets to appear as received without appearing as sent by the tester. > * UNH to look at enabling an SSH jump host server, to work around VPN > issues. > * Dynamic Config DTS test case is still disabled > * https://bugs.dpdk.org/show_bug.cgi?id=3D639 > * Need to confirm the patch status within DTS, looks like it was merge= d > 8-days ago. > * Mellanox testing disabled > * DTS seems to be sending packets out the wrong ports, flipping TX/RX > ports in code seems to fix this. Root cause is unknown. Can not upgrade > DTS / TRex because of the blocking issue listed above. > * Unit testing failures > * Still seeing random failures on the Func_reentrancy_autotest unit > test. 3 of the last 5 unit test failures are this test. Failures do not > seem related to OS, Virtual or Bare-metal, or architecture. > * Aaron is going to create a bug for this, and will look into removing > the test case from the suite for now. > * ASAN deployment > * Various memory leak fixes in patchworks > * rte_pci_scan > * > http://patches.dpdk.org/project/dpdk/patch/20210616065257.16044-1-david.m= archand@redhat.com/ > * ribv6 > * > http://patches.dpdk.org/project/dpdk/patch/20210616181833.356159-1-ohilya= rd@iol.unh.edu/ > * cmdline autotest > * > http://patches.dpdk.org/project/dpdk/patch/20210616180724.355217-1-ohilya= rd@iol.unh.edu/ > * test_eal_flags > * > http://patches.dpdk.org/project/dpdk/patch/20210616162453.349614-1-ohilya= rd@iol.unh.edu/ > * flow_classify > * > http://patches.dpdk.org/project/dpdk/patch/20210616195724.366103-1-ohilya= rd@iol.unh.edu/ > * Still more leaks in unit tests, which prevent deployment. > * Periodic Testing > * Run daily, but only if the git HEAD has moved. > * Branches (pointing to the default of the repos): > * dpdk main branch > * dpdk-next-net > * dpdk-next-virtio > * dpdk-next-eventdev > * dpdk-next-crypto > * LTS current and previous (i.e. DPDK release plan) (e.g. 20.11 and > 19.11 currently) > * Test cases: > * mtu_update > * scatter > * unit_tests_mbuf > * stats_checks > * dynamic_config > * Planned, but disabled due to > https://bugs.dpdk.org/show_bug.cgi?id=3D639 > * mac_filter > * link_status_interrupt > * nic_single_core_perf > * Should the lab run ABI/Compile/Unit testing periodically? > * Daily, same triggers as described above > * When and where should the lab send an email? > * Every run (both pass & fail) > * On failure > * Something else? > * To maintainers, devs mailing list, somewhere else? > * Send the reports to the test-reports mailing list. In the future > we will need to align the report formatting between labs. CC the > maintainers for what was tested.. > * How often should these be run? > * Daily if there are any changes (Current) > * rte flow > * Will be deployed alongside periodic testing, to provide a way to > test systems while failures are addressed by the maintainers > * Clang Cross-compile Testing > * Failure to build. Related to event/cnxk/cnxk_tim_worker. > * Bug submitted to https://bugs.dpdk.org/show_bug.cgi?id=3D740 > * Production pipeline is set up to enable this test once this bug is > resolved > * FreeBSD 13 > * Now doing compile and ABI testing > * Unit testing blocked by contigmem-related issue > * Clock skew issue resolved > * Patch applied to IOL infrastructure and merged into DTS > * ABI False failures > * Last week (June 4), a couple of false failures were caused by > compiler updates (i.e. updating container images after the ABI reference > was generated). The lab saves off the reference as an optimization. The > lab systems were updated to regenerate the ABI references if container > images are updated. > * aarch64 SVE testing > * With Ccache enabled, builds take about 5 to 7 minutes within the > emulated environment. This will keep the compile and binarys in the sam= e > environment (i.e. within a single container). > > --------------------------------------------------------------------- > Intel Lab > > * Patchwork Series https://bugs.dpdk.org/show_bug.cgi?id=3D718 > * It=E2=80=99s on-going, and we have found the root cause. The solutio= n is a > little complicated in CI script, and needs more time to fix them. > * Some of the Intel test bed is off-line (for valid reasons, i.e. > debugging or development), this can block the reporting. Some workaround > have been made, will disable the test-bed if there is a need to offline i= t. > And if it is offline unexpectedly, CI will notify CI maintainers. > * Test reports mailing list was created for DTS, but patchwork needs to b= e > set up to monitor this list. Lijuan will send an example email report to > Ali. > * http://mails.dpdk.org/archives/dts-test-report/2021-June/000005.html > * http://mails.dpdk.org/archives/dts-test-report/2021-June/subject.html > * Also need to add the email list onto the webpage for > https://www.dpdk.org/contribute/#mailing-lists > > --------------------------------------------------------------------- > Github Actions / OBS > > * Github no changes. > * OBS no changes. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 / Test Development > > * DTS Improvement > * Discussions are progressing. Work is being tracked here: > https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DG= usy4yM/edit > * Next Meeting: TBD (working around vacation schedules) > * Developer Retesting Request > * https://mails.dpdk.org/archives/ci/2021-May/001189.html > * Seeking feedback on the =E2=80=9Ccommand syntax.=E2=80=9D Still nee= d to implement > the tracking / mechanics for things like patches and message ID tracking. > * Community Lab Objectives > * Q1 Update to the techboard: > https://docs.google.com/document/d/1v0VKtZdsMXg35WNDawdsnqj5J4Xl9Egu_4180= ukKD2o > * Status tracking is also being partly carried out in Bugzilla. Epics > have been created for each major objective. This will span 2021, do not > expect them to be closed quickly. Updates posted to each objective will > track story completion, etc. This is a compromise of how to easily track > the long term objectives. > * Open Requests (outside of planned objectives) > * Add meson syntax check testing ( > https://bugs.dpdk.org/show_bug.cgi?id=3D696) > * Will leave this open for now for folks to give feedback on. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 CI Meeting: June 30, 1pm UTC > > > > -- > > *Lincoln Lavoie* > > Principal Engineer, Broadband Technologies > > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > > lylavoie@iol.unh.edu > > https://www.iol.unh.edu > > +1-603-674-2755 (m) > > *Error! Filename not specified.* > > > > > -- > > *Lincoln Lavoie* > > Principal Engineer, Broadband Technologies > > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > > lylavoie@iol.unh.edu > > https://www.iol.unh.edu > > +1-603-674-2755 (m) > > [image: Image removed by sender.] > --0000000000003e5b8f05c5456cc0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Zhaoyan,



"[v2] lib/rte_r= ib6: fix stack buffer overflow" will be getting a v3 once priority wor= k in our CI environment is completed. Most of these are fairly minor patche= s, with the exception of that one.=C2=A0

I'= ;ll look into testing with this patch once we don't see any more leaks = when running the unit tests, but that may take a while.=C2=A0
Should this patch help mitigate some of the memory allocation p= roblems we've seen in the unit tests when ASAN is enabled?
Owen

On Fri, Jun 18, 2021 at 4:17 AM Chen, Zhaoyan <zhaoyan.chen@intel.com> wrot= e:

Great Lincoln.

=C2=A0

Could you kindly share the patch links?

=C2=A0

/Zhaoyan

=C2=A0

From: = Lincoln Lavoie <lylavoie@iol.unh.ed= u>
Date: Friday, June 18, 2021 at 09:55
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: "ci@dpdk.o= rg" <ci@dpdk.o= rg>, "Lin, Xueqin" <xueqin.lin@intel.com>, Owen Hilyard <ohilyard@iol.unh.edu>
Subject: Re: [dpdk-ci] June 17 Community CI Meeting Minutes

=C2=A0

Hi=C2=A0Zhaoyan,

=C2=A0<= /span>

Owen from our team ha= s been leading the efforts on getting ASAN running on (under, with) DPDK.= =C2=A0 He's got a couple of patches submitted fixing some smaller issue= s he's seen.=C2=A0 I think David Marchand also had some patches started to fix some of the issues as well.

=C2=A0<= /span>

Cheers,
Lincoln

=C2=A0

Hi, Lincoln,

=C2=A0

For * ASAN deployment, what kind of tests are you going to depl= oy?

=C2=A0=

We hav= e a patch for enable ASAN for DPDK. I don=E2=80=99t know if is it helpful..=

http://patches.dpdk.org/project/dp= dk/patch/20210615081205.101071-1-zhihongx.peng@intel.com/

=C2=A0=

Thanks

=C2=A0

/Zhaoyan

=C2=A0

From: ci <ci-bounces@dpdk.org> on b= ehalf of Lincoln Lavoie <lylavoie@iol.unh.edu>
Date: Thursday, June 17, 2021 at 23:48
To: "ci@dpdk.o= rg" <ci@dpdk.o= rg>
Subject: [dpdk-ci] June 17 Community CI Meeting Minutes

=C2=A0

June 17, 2021

#####################################################################
Attendees

1. Lincoln Lavoie
2. Brandon Lo
3. Owen Hilyard
4. Aaron Conole
5. Ali Alnubani
6. Juraj Linke=C5=A1
7. Lijuan Tu
8. Ashley Weltz
9. Thomas Monjalon
10. Michael Santana
11. David Marchand

#####################################################################
Agenda

1. Performance Metric Change to Percentage
2. Coverity Testing
3. CI Lab Status
4. Test Development
5. 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
Performance Metric Change to Percentage

* Patch series is still pending merge: https://patchwork.dpdk.org/project/dts/list/?series=3D15990
* Blocked by: https://bugs.dpdk.org/show_bug.cgi?id=3D670
* Blocks any upgrade to the latest DTS versions, which depend on the latest= TRex.
* A work around could be to skip testing specific frame sizes that cause th= at issue. Ali will confirm internally and reply back to the lab on this way= forward.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Coverity Testing

* https://bugs.dpdk.org/show_bug.cgi?id=3D719
* Need to investigate if the lab can set up a way to desktop analysis, whic= h would run local to the systems.=C2=A0 Request is to run the test per patc= h, to check for additional issues being introduced by the patch.=C2=A0 Only= reports new defects.
* https://community.synopsys.com/s/topic/0TO34000000LJdaGAG/coverity-desktop-= analysis I think this is not an article (just Q&A), you might have = to check the documentation in your local installation
* Need to verify the requirements for running the tool, and if it required = a paid account, etc.

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

---------------------------------------------------------------------
UNH-IOL Community Lab

* Currently looking into 40G Intel machine issues.
=C2=A0 =C2=A0* Stats checks disabled due to the requirement for VM images f= or the test suite in newer DTS versions
=C2=A0 =C2=A0* MTU update test suite disabled due to issue of unknown origi= n causing packets to appear as received without appearing as sent by the te= ster.
=C2=A0 =C2=A0* UNH to look at enabling an SSH jump host server, to work aro= und VPN issues.
* Dynamic Config DTS test case is still disabled
=C2=A0 =C2=A0* =C2=A0https://bugs.dpdk.org/show_bug.cgi?id=3D639
=C2=A0 =C2=A0* Need to confirm the patch status within DTS, looks like it w= as merged 8-days ago.
* Mellanox testing disabled
=C2=A0 =C2=A0* DTS seems to be sending packets out the wrong ports, flippin= g TX/RX ports in code seems to fix this.=C2=A0 Root cause is unknown.=C2=A0= Can not upgrade DTS / TRex because of the blocking issue listed above.
* Unit testing failures
=C2=A0 =C2=A0* Still seeing random failures on the Func_reentrancy_autotest= unit test. =C2=A03 of the last 5 unit test failures are this test.=C2=A0 F= ailures do not seem related to OS, Virtual or Bare-metal, or architecture.<= br> =C2=A0 =C2=A0* Aaron is going to create a bug for this, and will look into = removing the test case from the suite for now.
* ASAN deployment
=C2=A0 =C2=A0* Various memory leak fixes in patchworks
=C2=A0 =C2=A0 =C2=A0 * rte_pci_scan
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* http://patches.dpdk.org/project/dpdk/patch/20210616065257.16044-1-david.mar= chand@redhat.com/
=C2=A0 =C2=A0 =C2=A0 * ribv6
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* http://patches.dpdk.org/project/dpdk/patch/20210616181833.356159-1-ohilyard= @iol.unh.edu/
=C2=A0 =C2=A0 =C2=A0 * cmdline autotest
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* http://patches.dpdk.org/project/dpdk/patch/20210616180724.355217-1-ohilyard= @iol.unh.edu/
=C2=A0 =C2=A0 =C2=A0 * test_eal_flags
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* http://patches.dpdk.org/project/dpdk/patch/20210616162453.349614-1-ohilyard= @iol.unh.edu/
=C2=A0 =C2=A0 =C2=A0 * flow_classify
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* http://patches.dpdk.org/project/dpdk/patch/20210616195724.366103-1-ohilyard= @iol.unh.edu/
=C2=A0 =C2=A0* Still more leaks in unit tests, which prevent deployment. * Periodic Testing
=C2=A0 =C2=A0* Run daily, but only if the git HEAD has moved.
=C2=A0 =C2=A0* Branches (pointing to the default of the repos):
=C2=A0 =C2=A0 =C2=A0 * dpdk main branch
=C2=A0 =C2=A0 =C2=A0 * dpdk-next-net
=C2=A0 =C2=A0 =C2=A0 * dpdk-next-virtio
=C2=A0 =C2=A0 =C2=A0 * dpdk-next-eventdev
=C2=A0 =C2=A0 =C2=A0 * dpdk-next-crypto
=C2=A0 =C2=A0 =C2=A0 * LTS current and previous (i.e. DPDK release plan) (e= .g. 20.11 and 19.11 currently)
=C2=A0 =C2=A0* Test cases:
=C2=A0 =C2=A0 =C2=A0 * mtu_update
=C2=A0 =C2=A0 =C2=A0 * scatter
=C2=A0 =C2=A0 =C2=A0 * unit_tests_mbuf
=C2=A0 =C2=A0 =C2=A0 * stats_checks
=C2=A0 =C2=A0 =C2=A0 * dynamic_config
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Planned, but disabled due to https://bugs.dpdk.org/show_bug.cgi?id=3D639
=C2=A0 =C2=A0 =C2=A0 * mac_filter
=C2=A0 =C2=A0 =C2=A0 * link_status_interrupt
=C2=A0 =C2=A0 =C2=A0 * nic_single_core_perf
=C2=A0 =C2=A0* Should the lab run ABI/Compile/Unit testing periodically? =C2=A0 =C2=A0 =C2=A0 * Daily, same triggers as described above
=C2=A0 =C2=A0* When and where should the lab send an email?
=C2=A0 =C2=A0 =C2=A0 * Every run (both pass & fail)
=C2=A0 =C2=A0 =C2=A0 * On failure
=C2=A0 =C2=A0 =C2=A0 * Something else?
=C2=A0 =C2=A0 =C2=A0 * To maintainers, devs mailing list, somewhere else? =C2=A0 =C2=A0 =C2=A0 * Send the reports to the test-reports mailing list.= =C2=A0 In the future we will need to align the report formatting between la= bs.=C2=A0 CC the maintainers for what was tested..
=C2=A0 =C2=A0* How often should these be run?
=C2=A0 =C2=A0 =C2=A0 * Daily if there are any changes (Current)
=C2=A0 =C2=A0* rte flow
=C2=A0 =C2=A0 =C2=A0 * Will be deployed alongside periodic testing, to prov= ide a way to test systems while failures are addressed by the maintainers * Clang Cross-compile Testing
=C2=A0 =C2=A0* Failure to build. Related to event/cnxk/cnxk_tim_worker.
=C2=A0 =C2=A0* Bug submitted to https://bugs.dpdk.org/show_bug.cgi?id=3D740
=C2=A0 =C2=A0* Production pipeline is set up to enable this test once this = bug is resolved
* FreeBSD 13
=C2=A0 =C2=A0* Now doing compile and ABI testing
=C2=A0 =C2=A0* Unit testing blocked by contigmem-related issue
* Clock skew issue resolved
=C2=A0 =C2=A0* Patch applied to IOL infrastructure and merged into DTS
* ABI False failures
=C2=A0 =C2=A0* Last week (June 4), a couple of false failures were caused b= y compiler updates (i.e. updating container images after the ABI reference = was generated).=C2=A0 The lab saves off the reference as an optimization.= =C2=A0 The lab systems were updated to regenerate the ABI references if container images are updated.
* aarch64 SVE testing
=C2=A0 =C2=A0* With Ccache enabled, builds take about 5 to 7 minutes within= the emulated environment.=C2=A0 This will keep the compile and binarys in = =C2=A0the same environment (i.e. within a single container).

---------------------------------------------------------------------
Intel Lab

* Patchwork Series https://bugs.dpdk.org/show_bug.cgi?id=3D718
=C2=A0 =C2=A0* It=E2=80=99s on-going, and we have found the root cause. The= solution is a little complicated in CI script, and needs more time to fix = them.
* Some of the Intel test bed is off-line (for valid reasons, i.e. debugging= or development), this can block the reporting. Some workaround have been m= ade, will disable the test-bed if there is a need to offline it. And if it = is offline unexpectedly, CI will notify CI maintainers.
* Test reports mailing list was created for DTS, but patchwork needs to be = set up to monitor this list.=C2=A0 Lijuan will send an example email report= to Ali.
* http://mails.dpdk.org/archives/dts-test-report/2021-June/000005.html * http://mails.dpdk.org/archives/dts-test-report/2021-June/subject.html * Also need to add the email list onto the webpage for https://www.dpdk.org/contribute/#mailing-lists

---------------------------------------------------------------------
Github Actions / OBS

* Github no changes.
* OBS no changes.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 / Test Development

* DTS Improvement
=C2=A0 =C2=A0* Discussions are progressing. Work is being tracked here: https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGus= y4yM/edit
=C2=A0 =C2=A0* Next Meeting: TBD (working around vacation schedules)
* Developer Retesting Request
=C2=A0 =C2=A0* https://mails.dpdk.org/archives/ci/2021-May/001189.html
=C2=A0 =C2=A0* Seeking feedback on the =E2=80=9Ccommand syntax.=E2=80=9D = =C2=A0Still need to implement the tracking / mechanics for things like patc= hes and message ID tracking.
* Community Lab Objectives
=C2=A0 =C2=A0* Q1 Update to the techboard: https://docs.google.com/document/d/1v0VKtZdsMXg35WNDawdsnqj5J4Xl9Egu_4180uk= KD2o
=C2=A0 =C2=A0* Status tracking is also being partly carried out in Bugzilla= .=C2=A0 Epics have been created for each major objective. This will span 20= 21, do not expect them to be closed quickly. Updates posted to each objecti= ve will track story completion, etc.=C2=A0 This is a compromise of how to easily track the long term objectives.
* Open Requests (outside of planned objectives)
=C2=A0 =C2=A0* Add meson syntax check testing (https://bugs.dpdk.org/show_bu= g.cgi?id=3D696)
=C2=A0 =C2=A0 =C2=A0 * Will leave this open for now for folks to give feedb= ack on.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 CI Meeting: June 30, 1pm UTC

=C2=A0

--

Lincoln Lavoie

Principal Engineer, Broadband Technologies=

21 Madbury Rd., Ste. 100, Durham, NH 03824=

+1-603-674-2755 (m)


=C2=A0

--

Lincoln Lavoie

Principal Engineer, Broadband Technologies=

21 Madbury Rd., Ste. 100, Durham, NH 03824=

+1-603-674-2755 (m)

3D"Image

--0000000000003e5b8f05c5456cc0--