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 8FF3942653; Wed, 27 Sep 2023 18:31:34 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 870C1402F2; Wed, 27 Sep 2023 18:31:34 +0200 (CEST) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) by mails.dpdk.org (Postfix) with ESMTP id 71B944026B for ; Wed, 27 Sep 2023 18:31:33 +0200 (CEST) Received: by mail-ot1-f51.google.com with SMTP id 46e09a7af769-6c4bf619b57so5696168a34.1 for ; Wed, 27 Sep 2023 09:31:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1695832292; x=1696437092; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ZP5/xkU/7lMBRAt9UA84JPiQGSqdpHo7SrL4RJSfC1U=; b=XB1U04ZJNzAbuHXy+Gb/br7nVPU+LB14astqtfPE83wzFb7YM3MrKwfM0O8ZnmMirC ZJ3a/OKM17W0CZy1FZyXSTk/q7w7JBKLZIx8XoVf+gyi4d3Rh3nuFAYjoNT5D4qxBydE GAX/1mWeSZxEiSgNH1S9rvLusCdVICKGS3BJE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695832292; x=1696437092; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZP5/xkU/7lMBRAt9UA84JPiQGSqdpHo7SrL4RJSfC1U=; b=NLpj9HGKrGkgSmuE9fyUjdonq/OarLydpTy5D1bYCdQbwBps+aMSxhbhpBLhGuJXnA claPOT93LHw1uOPo1GLgunP4X6BrRthoVn8uot46lhzwiIvHrcDf8LojIAlO7H1HMhP7 R0mxRCbW/LMzBirMS0nCgWt7UhI8O1Iq8+7EHfMNyxBCnDYeCdjLZkAyPIKdAS+BRH3q eJhEeG1778G9ixWbuRyENZ6+VrLJU1byZn9vRQy7cbNQl7ff8YitLrkNGWip/xubR/Iq h2fYiAROJX8bTxHREmdNJXHs5NgER40T72Ln3EjcvG8TcsVQRdUrk9Pptsnm62LIqqNJ 7CVw== X-Gm-Message-State: AOJu0Yxa1w0e+eQJErpCFhgQcVCkG1pLX27KIYfgux7usLF+pilQjYGH iAV2JB4l/6fx1Ok696TgIXDFPfOPNA/IqJHHkTX3mjRPo7mWqmqkxVI= X-Google-Smtp-Source: AGHT+IGqM8/0FmXVnGesGkTCIEK0oETjPRxBnqLwA7TgovvG403IzqdCzsQcs9D30VbVL7kBE1G+Lj1JHTC6LJMeqzU= X-Received: by 2002:a05:6830:1e85:b0:6bd:b5f7:187a with SMTP id n5-20020a0568301e8500b006bdb5f7187amr2655947otr.20.1695832292646; Wed, 27 Sep 2023 09:31:32 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Wed, 27 Sep 2023 12:31:22 -0400 Message-ID: Subject: Apply Patchseries Script To: ci@dpdk.org Content-Type: multipart/alternative; boundary="000000000000671fb7060659b9cf" 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 --000000000000671fb7060659b9cf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all, The Community Lab is reviewing and rewriting some parts of our (currently internal) apply patchseries script. The reasons are: 1. We want to remove any dependency the apply script has on our internal infrastructure, so that it can be upstreamed and utilized by others in the community. 2. We want to add in new features like =E2=80=9Cdepends-on patch=E2=80=9D a= pplying (like ovsrobot is doing currently) 3. Some DPDK project processes have changed (like moving next branches from the main repo to being their own distinct repos). We have added on workarounds along the way to account for this, but an overall rework is now in order to clean up our process. Before we do the work and attempt to upstream the script, I want to verify with the community that our current assumptions regarding the apply patchseries process are appropriate and should not be tweaked. Assumptions: 1. There are two inputs, A. The pw series url and B. The branch output of pw_maintainers_cli.py 2. Do not apply and run if the series is an RFC series 3. Always check out to the current head of tree when applying a patch, regardless of whether the tree state has changed between patch submission and patch application in CI. 4. If the cover letter contains =E2=80=9Cdepends-on,=E2=80=9D extract the d= ependency series id(s), apply those, then attempt to apply the patch 5. If patch does not cleanly apply to the branch supplied by pw_maintainers_cli.py, attempt to apply on dpdk main. If this also fails, report an apply failure. 6. If apply is successful, attempt a sanity build, and report a build failure if that fails. If it succeeds, proceed with all CI testing. Note: The Community Lab does not currently use pw-client. If it is better for the CI community, we could stop maintaining a dedicated script for the apply process, try moving the pw-client, and direct our efforts at patching pw-client with the goal of adding support for features like depends-on. Are other labs using pw-client right now and do you recommend it? --000000000000671fb7060659b9cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello all,


The Community Lab is reviewing and rewritin= g some parts of our (currently internal) apply patchseries script. The reas= ons are:

1. We want to remove any dependency the apply script has on= our internal infrastructure, so that it can be upstreamed and utilized by = others in the community.=C2=A0

2. We want to add in new features like= =E2=80=9Cdepends-on patch=E2=80=9D applying (like ovsrobot is doing curren= tly)

3. Some DPDK project processes have changed (like moving next br= anches from the main repo to being their own distinct repos). We have added= on workarounds along the way to account for this, but an overall rework is= now in order to clean up our process.=C2=A0

Before we do the wo= rk and attempt to upstream the script, I want to verify with the community = that our current assumptions regarding the apply patchseries process are ap= propriate and should not be tweaked. Assumptions:

1. There are two in= puts, A. The pw series url and B. The branch output of pw_maintainers_cli.p= y

<= /span>2. Do not apply and run if the series is an RFC series

<= span style=3D"font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);= background-color:transparent;font-variant-numeric:normal;font-variant-east-= asian:normal;font-variant-alternates:normal;vertical-align:baseline">3. Alw= ays check out to the current head of tree when applying a patch, regardless= of whether the tree state has changed between patch submission and patch a= pplication in CI.

4. If the cover letter contains =E2=80=9Cdepends-on= ,=E2=80=9D extract the dependency series id(s), apply those, then attempt t= o apply the patch

5. If patch does not cleanly apply to the branch su= pplied by pw_maintainers_cli.py, attempt to apply on dpdk main. If this als= o fails, report an apply failure.=C2=A0

6. If apply is successful, at= tempt a sanity build, and report a build failure if that fails. If it succe= eds, proceed with all CI testing.


Note: The Community Lab does not= currently use pw-client. If it is better for the CI community, we could st= op maintaining a dedicated script for the apply process, try moving the pw-= client, and direct our efforts at patching pw-client with the goal of addin= g support for features like depends-on. Are other labs using pw-client righ= t now and do you recommend it?


--000000000000671fb7060659b9cf--