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 5C8AD46B4A; Fri, 11 Jul 2025 19:56:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5702A402CB; Fri, 11 Jul 2025 19:56:31 +0200 (CEST) Received: from mail-pg1-f178.google.com (mail-pg1-f178.google.com [209.85.215.178]) by mails.dpdk.org (Postfix) with ESMTP id 216C14021E for ; Fri, 11 Jul 2025 19:56:29 +0200 (CEST) Received: by mail-pg1-f178.google.com with SMTP id 41be03b00d2f7-b31f0ef5f7aso1473215a12.3 for ; Fri, 11 Jul 2025 10:56:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1752256588; x=1752861388; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=gsyMcG/XVxMtYRl3zDpHI4jhjXtJ9II42KeJTpnc/5s=; b=WlZddKQ5YaMRKDNTMvR7xXUeA9nrPCVkoYETqaGHynQoHnlleie0hNFUgbNpnuabQZ BwOywpHfq5z+cgcXZ/5rXTJO20n01LjrUmU8evuz7vvGwXrCWdAoZZkif4mJ/426FKjG SMvaHC1IhKtz1H+DzLm0+G5nbmUDf7cDNxb5k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752256588; x=1752861388; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gsyMcG/XVxMtYRl3zDpHI4jhjXtJ9II42KeJTpnc/5s=; b=CW02mFDUf0iyjT8DEZ4UsRKq1B8inV6NXdPrm+dB7N6Ae2vzf/HV/R2ywZVTwCeYR1 +OaC3PgsEsR/Vx1P1tHN9qpfstTUWBsm0jjlH1tlb4v0ilDl1sC9L8wtxB3FMq/tFJoe R5yfUAz9BqbpS+u7dqFQQ0bpFzu4fxmE8UZUighNE5yAE6bHzPAhDLbOBleOJzTOBqza 369CkzYTWGl1RJmJz44Y0Xo8mTltpc1hIEltLOoB7b3YJZdzFLY6xRZLZWnTF/+NAIDJ t0WsHz5rBU5IAD9XiJXURNUNCjiveA/PeFRi6gTwLi2t6MuaRfkBDQ9BhSqcUF5TKU30 Ftpg== X-Gm-Message-State: AOJu0YyptokIkaj6BiAFP4P2yXiEx4FPHg0+IiFewt55cbQzhuTXfiuJ qxPXuYb/9vfP3rnWYxfJiFYCNOkLXkgWxb5gubiDbs4DUpGjkgjNhNDffj+iaXzWe/3Fh4IA2OV tzU329exhuoZaoTTmkLVVaODPkxdIlWiULkhn0cs+NI+l6kCHaDx95m4= X-Gm-Gg: ASbGncsjgj010xoWBtsZFDDQ+tgQu7MSU4Z09CXkRjjCvONoNe3CvZQWh8/ZmggK4i6 hKsPnTibegqfahdRb37Zi6wGZc2l6tq2kD93/QNcFGINZvQCdlgzQPeDM7UWgiVQM3JdQVEnhrI sVKM1jbOUVHRmLyAwJw+MssXC3VVTJJs2EY67E4N17sQRMwIYo5NBNgEQ0YO4VVN0kDF0PnsbXE PJeW768UGno/nj6trEMrFIaRoCwyymvLpzSK/zq X-Google-Smtp-Source: AGHT+IGZjkRHuM13LLU92Ni6PX3iWaqFZ79oCeo8QmjeewlzHULv2nlVbHvCRb4QfM7Z05k3LtJ8fSQDUyALcE6ElFc= X-Received: by 2002:a17:90a:e18e:b0:31c:38f8:7efb with SMTP id 98e67ed59e1d1-31c4f573322mr6319276a91.18.1752256586760; Fri, 11 Jul 2025 10:56:26 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Fri, 11 Jul 2025 13:50:41 -0400 X-Gm-Features: Ac12FXyjRngfRcBnLXEKVutTtxzdlQggL5DumDcTqoBPThxHGFxN_qZdcdaXeMs Message-ID: Subject: Community CI Meeting Minutes - July 9, 2025 To: ci@dpdk.org Cc: dev , Aaron Conole , Dean Marx , Adam Hassick , "Brandes, Shai" , zhoumin , "Puttaswamy, Rajesh T" Content-Type: multipart/alternative; boundary="00000000000068d93a0639ab07c2" 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 --00000000000068d93a0639ab07c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ##################################################################### July 9, 2025 Attendees 1. Patrick Robb 2. Manit Mahajan 3. Dean Marx 4. Luca Vizzarro 5. Shai Brandes 6. Aaron Conole ##################################################################### 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 * Expected remaining RC schedule: * RC3 - July 9-10 (today/tomorrow) * DTS HEAD has been run with the check scripts, done a docs build, and run some PF and VF tests (all working) * Tech board will have a discussion this morning about =E2=80=9CVLAN tag an= d QinQ stripping in DPDK.=E2=80=9D * The behavior is not clearly defined, and should be standardized. * Results from the =E2=80=9Cwhen to meet=E2=80=9D survey: https://www.when2meet.com/?30965992-3ijyI * Basically, options going forward are Tuesdays from 12:00 UTC to 14:00 UTC, Wednesdays from 13:00 UTC to 14:00 UTC, and Thursdays from 12:00 UTC to 13:00 UTC. * Next meeting will be at 12:00 UTC on Thursday the 24th * DPDK-CI Test Recheck script has been updated to capture the =E2=80=9Creba= se=E2=80=9D flag for rebasing onto specific branches by developer request: * https://patchwork.dpdk.org/project/ci/patch/20250611205849.72165-1-probb@io= l.unh.edu/ * https://core.dpdk.org/testing/#requesting-a-patch-retest * /events/ PW rework * Agree: support project filtering for /events/ * Adam Hassick and Aaron to work on this. * Aaron will come up to UNH in a few weeks to attack this, and ensure it works for multiple projects he is involved with =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 --------------------------------------------------------------------- AWS Lab * Test recheck support plans: * This has been implemented, and should be live now. * We will need to update the DPDK website to indicate the support is now live * If no rebase flag is included, they re-test the original artifact. * Some other labs report new results with the retest count, and Amazon will aim to do the same * The value is that it=E2=80=99s not obvious from the UI whether the = recheck has happened/is complete. * AWS infra failures: * Apply failures are sending a generic fail, and also running unit tests and reporting the unit test logs * Correct behavior is to stop testing when the apply failure happens, and send an =E2=80=9Capply failure=E2=80=9D report to test-report mailing l= ist * Status: Solved * David noticed some failures due to timeout on the telemetry test, other CIs extend the timeout with the -t arg: * Status: Using -t 60 now * Review on apply failure on .rst files discussion from the previous meetin= g * They are skipping the release notes in each patch. --------------------------------------------------------------------- UNH-IOL Community Lab * Apply patchset process: Skipping making a tarball if the patch is a docs patch only. * Labeling as =E2=80=9Cnot applicable=E2=80=9D on the lab dashboard * There were some patches with code in them which were marked as =E2=80= =9CDOCS ONLY=E2=80=9D by create_series_artifact.py. We have overridden this by putt= ing in testing for these series, and we are debugging the script. * Windows Builds: * Status: MSVC drivers enable had a compile failure due to MLX5. * This is because the drivers enable series has a series dependency which has not yet been merged. * Arm Grace E810: * There were some failures for the E810 NIC for an ICE PMD patch because it updated the 16byte ICE PMD descriptors flag for Meson, so it was no longer getting used by our testing and consequently MPPS was reduced about 6%. * There were some unrelated infra fails for this system yesterday. We resolved the issue and put in retets. PW is =E2=80=9Call green.=E2=80=9D * Patchwork polling: * Manit is working on refactoring our patchwork polling series. * DTS: * Some new testsuites have been merged, and will be pulled into mainline for RC3 imminently. We need to add these new testsuites to DTS configs at the lab. * Our CI server fell over last Thursday, which caused us to have to rerun testing all Thursday patchseries on Thursday evening. We were caught up by Friday evening. --------------------------------------------------------------------- Intel Lab * Did not get any responses from the Intel lab maintainer to the =E2=80=9Cs= chedule a meeting=E2=80=9D poll. --------------------------------------------------------------------- Github Actions Robot * AI initiative (patch review bot): * Based on sourcery.ai * Aaron has investigated the GH rest api about Pull Requests, comments, etc. And he thinks it will be possible to pull the comments for a hunk which has been added, and send emails to the mailing list (or at least to the offer) with review comments. These emails can include links to the github comments. * Will require setting up an alternative mirror repo and giving the robot extra permissions on this repo * Status: In progress, but may require more feedback from Jerin, David, etc. --------------------------------------------------------------------- Loongson Lab * Patchseries recheck support: Min Zhou has tested out the new version of the get_reruns.py script, and has indicated he will use it to support the rebase argument. * When this happens we need to update the DPDK website testing page to update the supported labs list * Patrick Robb can submit the website update. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 * Merged since the previous meeting: * Virtual Function testing: * Packet forwarding from DTS created VFs is working (on mellanox and broadcom, still figuring out if our Intel NICs are misconfigured for promisc mode). * Important decisions to clarify: * The way that it works is that it sets 1 (and only 1) VF per PF, and re-sets SUT ingress, SUT egress to the new virtual functions. * It runs the exact same tests as the PFs * Some testsuites are decorated with a specific PF_Required, capability, meaning those are forced to skip. * Rte_flow testing: * There are some cases where Flow validate says =E2=80=9Ccan create t= his flow rule=E2=80=9D and then flow create says =E2=80=9CI cannot create this=E2=80= =9D for various PMDs. Dean is going to document these on Bugzilla and CC Flow and PMD maintainers. This is pretty low hanging fruit. * There are some other failures on some devices which are more involved, and will be documented separately. * Add generic blocking app class (now superclass of DPDK blocking app class) * Rework test results series * It provides the =E2=80=9CReason=E2=80=9D for the failure inline alo= ngside the result in the results.json and result_summary.txt * These should all get pulled from next-dts to mainline imminently. * Moved to the next release: * Single_core_forwarding test and TREX support: * This is running fine but the review of the v3 suggested changes which were too significant to resolve at the end of this development cycle. * Qinq Testsuite * File manager / abstraction moved to the next release * Most straightforward solution (lazy approach) is using sftp * DTS Roadmap: * Work on the roadmap at the DTS call next Thursday. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Jul 24, 2025 --00000000000068d93a0639ab07c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
##########################################################= ###########
July 9, 2025
Attendees
1. Patrick Robb
2. Manit Mah= ajan
3. Dean Marx
4. Luca Vizzarro
5. Shai Brandes
6. Aaron Con= ole

################################################################= #####
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
* Expected remaining RC schedule:
=C2= =A0 =C2=A0* RC3 - July 9-10 (today/tomorrow)
=C2=A0 =C2=A0* DTS HEAD has= been run with the check scripts, done a docs build, and run some PF and VF= tests (all working)
* Tech board will have a discussion this morning ab= out =E2=80=9CVLAN tag and QinQ stripping in DPDK.=E2=80=9D
=C2=A0 =C2=A0= * The behavior is not clearly defined, and should be standardized.
* Res= ults from the =E2=80=9Cwhen to meet=E2=80=9D survey: https://www.when2meet.com/?30965992-3ijyI
=C2=A0 =C2=A0* Basically, options going forward are Tuesdays from 12:= 00 UTC to 14:00 UTC, Wednesdays from 13:00 UTC to 14:00 UTC, and Thursdays = from 12:00 UTC to 13:00 UTC.
=C2=A0 =C2=A0* Next meeting will be at 12:0= 0 UTC on Thursday the 24th
* DPDK-CI Test Recheck script has been update= d to capture the =E2=80=9Crebase=E2=80=9D flag for rebasing onto specific b= ranches by developer request:
=C2=A0 =C2=A0* http= s://patchwork.dpdk.org/project/ci/patch/20250611205849.72165-1-probb@iol.un= h.edu/
=C2=A0 =C2=A0* https://core.dpdk.org/testing/#requesting-a-patch-re= test
* /events/ PW rework
=C2=A0 =C2=A0* Agree: support project f= iltering for /events/
=C2=A0 =C2=A0* Adam Hassick and Aaron to work on t= his.
=C2=A0 =C2=A0 =C2=A0 * Aaron will come up to UNH in a few weeks to = attack this, and ensure it works for multiple projects he is involved with<= div>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=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

---------------------------------= ------------------------------------
AWS Lab
* Test recheck support p= lans:
=C2=A0 =C2=A0* This has been implemented, and should be live now.<= br>=C2=A0 =C2=A0* We will need to update the DPDK website to indicate the s= upport is now live
=C2=A0 =C2=A0* If no rebase flag is included, they re= -test the original artifact.
=C2=A0 =C2=A0* Some other labs report new r= esults with the retest count, and Amazon will aim to do the same=C2=A0
= =C2=A0 =C2=A0 =C2=A0 * The value is that it=E2=80=99s not obvious from the = UI whether the recheck has happened/is complete.
* AWS infra failures:=C2=A0 =C2=A0* Apply failures are sending a generic fail, and also runnin= g unit tests and reporting the unit test logs
=C2=A0 =C2=A0 =C2=A0 * Cor= rect behavior is to stop testing when the apply failure happens, and send a= n =E2=80=9Capply failure=E2=80=9D report to test-report mailing list
=C2= =A0 =C2=A0 =C2=A0 * Status: Solved
=C2=A0 =C2=A0* David noticed some fai= lures due to timeout on the telemetry test, other CIs extend the timeout wi= th the -t arg:
=C2=A0 =C2=A0 =C2=A0 * Status: Using -t 60 now
* Revie= w on apply failure on .rst files discussion from the previous meeting
= =C2=A0 =C2=A0* They are skipping the release notes in each patch.

--= -------------------------------------------------------------------
UNH-= IOL Community Lab
* Apply patchset process: Skipping making a tarball if= the patch is a docs patch only.
=C2=A0 =C2=A0* Labeling as =E2=80=9Cnot= applicable=E2=80=9D on the lab dashboard
=C2=A0 =C2=A0* There were some= patches with code in them which were marked as =E2=80=9CDOCS ONLY=E2=80=9D= by create_series_artifact.py. We have overridden this by putting in testin= g for these series, and we are debugging the script.
* Windows Builds:=C2=A0 =C2=A0* Status: MSVC drivers enable had a compile failure due to M= LX5.
=C2=A0 =C2=A0 =C2=A0 * This is because the drivers enable series h= as a series dependency which has not yet been merged.
* Arm Grace E810:<= br>=C2=A0 =C2=A0* There were some failures for the E810 NIC for an ICE PMD = patch because it updated the 16byte ICE PMD descriptors flag for Meson, so = it was no longer getting used by our testing and consequently MPPS was redu= ced about 6%.
=C2=A0 =C2=A0* There were some unrelated infra fails for t= his system yesterday. We resolved the issue and put in retets. PW is =E2=80= =9Call green.=E2=80=9D
* Patchwork polling:
=C2=A0 =C2=A0* Manit is w= orking on refactoring our patchwork polling series.
* DTS:
=C2=A0 =C2= =A0* Some new testsuites have been merged, and will be pulled into mainline= for RC3 imminently. We need to add these new testsuites to DTS configs at = the lab.
* Our CI server fell over last Thursday, which caused us to hav= e to rerun testing all Thursday patchseries on Thursday evening. We were ca= ught up by Friday evening.

-----------------------------------------= ----------------------------
Intel Lab
* Did not get any responses fr= om the Intel lab maintainer to the =E2=80=9Cschedule a meeting=E2=80=9D pol= l.

-----------------------------------------------------------------= ----
Github Actions Robot
* AI initiative (patch review bot):
=C2= =A0 =C2=A0* Based on sourcery.ai
=C2= =A0 =C2=A0* Aaron has investigated the GH rest api about Pull Requests, com= ments, etc. And he thinks it will be possible to pull the comments for a hu= nk which has been added, and send emails to the mailing list (or at least t= o the offer) with review comments. These emails can include links to the gi= thub comments.
=C2=A0 =C2=A0 =C2=A0 * Will require setting up an alterna= tive mirror repo and giving the robot extra permissions on this repo
=C2= =A0 =C2=A0* Status: In progress, but may require more feedback from Jerin, = David, etc.

--------------------------------------------------------= -------------
Loongson Lab
* Patchseries recheck support: Min Zhou ha= s tested out the new version of the get_reruns.py script, and has indicated= he will use it to support the rebase argument.
=C2=A0 =C2=A0* When this= happens we need to update the DPDK website testing page to update the supp= orted labs list
=C2=A0 =C2=A0* Patrick Robb can submit the website updat= e.
=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
* Merged since the pre= vious meeting:
=C2=A0 =C2=A0* Virtual Function testing:
=C2=A0 =C2=A0= =C2=A0 * Packet forwarding from DTS created VFs is working (on mellanox an= d broadcom, still figuring out if our Intel NICs are misconfigured for prom= isc mode).
=C2=A0 =C2=A0 =C2=A0 * Important decisions to clarify:
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* The way that it works is that it sets 1 (a= nd only 1) VF per PF, and re-sets SUT ingress, SUT egress to the new virtua= l functions.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* It runs the exact same = tests as the PFs
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Some testsuites are= decorated with a specific PF_Required, capability, meaning those are force= d to skip.
=C2=A0 =C2=A0* Rte_flow testing:
=C2=A0 =C2=A0 =C2=A0 * Th= ere are some cases where Flow validate says =E2=80=9Ccan create this flow r= ule=E2=80=9D and then flow create says =E2=80=9CI cannot create this=E2=80= =9D for various PMDs. Dean is going to document these on Bugzilla and CC Fl= ow and PMD maintainers. This is pretty low hanging fruit.
=C2=A0 =C2=A0 = =C2=A0 * There are some other failures on some devices which are more invol= ved, and will be documented separately.
=C2=A0 =C2=A0* Add generic block= ing app class (now superclass of DPDK blocking app class)
=C2=A0 =C2=A0*= Rework test results series
=C2=A0 =C2=A0 =C2=A0 * It provides the =E2= =80=9CReason=E2=80=9D for the failure inline alongside the result in the re= sults.json and result_summary.txt
=C2=A0 =C2=A0* These should all get pu= lled from next-dts to mainline imminently.
* Moved to the next release:<= br>=C2=A0 =C2=A0* Single_core_forwarding test and TREX support:
=C2=A0 = =C2=A0 =C2=A0 * This is running fine but the review of the v3 suggested cha= nges which were too significant to resolve at the end of this development c= ycle.
=C2=A0 =C2=A0* Qinq Testsuite
=C2=A0 =C2=A0* File manager / abs= traction moved to the next release
=C2=A0 =C2=A0 =C2=A0 * Most straightf= orward solution (lazy approach) is using sftp
* DTS Roadmap:
=C2=A0 = =C2=A0* Work on the roadmap at the DTS call next Thursday.

=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 Jul 24, 2025



--00000000000068d93a0639ab07c2--