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 E651E48A92; Mon, 3 Nov 2025 22:18:33 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BEE19402BB; Mon, 3 Nov 2025 22:18:33 +0100 (CET) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id 1A21A40299 for ; Mon, 3 Nov 2025 22:18:32 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-27d3540a43fso47841505ad.3 for ; Mon, 03 Nov 2025 13:18:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1762204711; x=1762809511; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dREsxMYkn9nE8vb9vkTdVhG5RJd4i7prPoWpGTKKmL4=; b=imDPnMyHsay15InXZLsYu2DRQqkINf2cuJygeCEQGVXtGhBn6NAwKRIjFUmIXaaZAG LVdErGX9poVmDUqy80NeA3V9J2VB51LmhOqAJOR8GZNjS8e5bGHmoVl5iAESY4lPqdUM rIsljyIBmnmjQAN8GEBjq+KKUZYlJDwGOrIXk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762204711; x=1762809511; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dREsxMYkn9nE8vb9vkTdVhG5RJd4i7prPoWpGTKKmL4=; b=sMLywqd6rBryzpIFOfImxpkisc5efjx41E/eMIE2GjVIHNjclQ4dbTCQ9HwnKYBBJo Z+/Stcl21anPhxMCSrBHqXJ6m78oO2KvABNRPW5CMeJD7iEq1cdIL+zw2Y9C1T6fADBE SaI0ZIrpF4AJPYQ7nix2C8iB2YF/2MGjcsC6kHKh0BkmUMeoRvNJxdqanVby1sKhuRKW I4DdHSD8F/hwGzwyxKRS7wxKNhhhTrjgp/9N3iUTDPJHjy9gvn3P7b2Dvk7iTcRKKBuD Hi+tBUt33lYEuTdVynrNtdlaBLptQVB7s+hN1Op7hUxpyLSPw3/MojoWjRNzK7MjHvRO OzWQ== X-Forwarded-Encrypted: i=1; AJvYcCWc80/Uf2YzH3g3R6T9nV5wnr32bWrT2WQxkQVE8rIhMt7Ngn7f4OnHSCv14CdO2bSyxg==@dpdk.org X-Gm-Message-State: AOJu0YxQZqbCLyeJyUvbOKXPSFV/RpV0o+o1qcVPEKAmxw8DdYrRTlSV 031e37Cf74qm0GYe5hsVY100Nv5jb9ll+Up0DkqkOu4RdOrvCbyoaNTFNad9p3A9P7Au4wjIN9/ b/bDpHR+Sg8Na+1nGCA1+5lF5eN/oU2tdOoKNFxkHYw== X-Gm-Gg: ASbGncstFpQg2bl603oKGDt8KtFBye6Fu7lPDpI1po27Fd/3htl0hjQuNdVpMEvoK/C 2rdK42htqQpdoCRZPSuaVKvkKaZD14n/AfTkp3Dum6jDysoX1nyZhoG8X1YEgIJ1DdynClbEzgY BN7iDG4LwgXvF/xNTePb6HSApZEjZXxgnMcnYpgn5SzsmO0KrpB1hm3A4oT+MmOEBk/a0wL/Ap8 8Z8rg1pSbZWjeZ0pQS1Py4UTCyPaPhN//NBbT5MJyziiRGQ9YymZ6Rpk7QyPD5GrYArXpiLO8VI Urh/R12zYw== X-Google-Smtp-Source: AGHT+IGSYKeS2NB15TLGVvNoL1mLcB6SZN0u79xUbqZM80hqX4F9KyOyniL+LPDCw/DiZAr8DQ/H1FDJnQZ6wvjPfGI= X-Received: by 2002:a17:903:2f8f:b0:249:3efa:3c99 with SMTP id d9443c01a7336-2951a600e39mr197663865ad.61.1762204711102; Mon, 03 Nov 2025 13:18:31 -0800 (PST) MIME-Version: 1.0 References: <98CBD80474FA8B44BF855DF32C47DC35F6551F@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> In-Reply-To: From: Patrick Robb Date: Mon, 3 Nov 2025 16:17:26 -0500 X-Gm-Features: AWmQ_blgZfZcgLSehZOhEPfIze1KsuQUFDyGeiHHDV65QLJ1Ss_cGQ1Uhs6hkN0 Message-ID: Subject: Re: Disable SPDK testing again? To: =?UTF-8?Q?Morten_Br=C3=B8rup?= Cc: David Marchand , bruce.richardson@intel.com, Aaron Conole , dpdk-techboard , ci@dpdk.org, dev Content-Type: multipart/alternative; boundary="000000000000d3bbae0642b74157" 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 --000000000000d3bbae0642b74157 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable All set. On Sun, Nov 2, 2025 at 8:06=E2=80=AFPM Patrick Robb wro= te: > Okay I'll push this change Monday morning. > > On Sat, Nov 1, 2025 at 3:47=E2=80=AFAM Morten Br=C3=B8rup > wrote: > >> > From: Patrick Robb [mailto:probb@iol.unh.edu] >> > Sent: Friday, 31 October 2025 16.13 >> > >> > On Fri, Oct 31, 2025 at 6:02=E2=80=AFAM Morten Br=C3=B8rup >> wrote: >> > >> >> If we disable SPDK testing due to this SPDK bug, how will we notice >> when they fix it, so we can enable SPDK testing again? >> > >> >> One option is I can disable SPDK testing for the "per-patch" testing, >> but leave it enabled for the periodic (once per 48 hours) runs on DPDK >> main. That way patch submitters aren't left wondering if their patch has >> broken SPDK, but we will be able to check in later on the DPDK main >> periodic builds to see if the SPDK side is fixed, at which point we can >> re-enable SPDK for per-patch testing. >> >> Yes, please do. >> >> --000000000000d3bbae0642b74157 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All set.

On Sun, Nov 2, 2025 at 8:06= =E2=80=AFPM Patrick Robb <probb@iol= .unh.edu> wrote:
Okay I'll push this change Monday morning.
On S= at, Nov 1, 2025 at 3:47=E2=80=AFAM Morten Br=C3=B8rup <mb@smartsharesystems.com&g= t; wrote:
> F= rom: Patrick Robb [mailto:probb@iol.unh.edu]
> Sent: Friday, 31 October 2025 16.13
>
> On Fri, Oct 31, 2025 at 6:02=E2=80=AFAM Morten Br=C3=B8rup <mb@smartsharesystems= .com> wrote:
>
>> If we disable SPDK testing due to this SPDK bug, how will we notic= e when they fix it, so we can enable SPDK testing again?
>
>> One option=C2=A0is I can disable SPDK testing for the "per-pa= tch" testing, but leave it enabled for the periodic (once per 48 hours= ) runs on DPDK main. That way patch submitters aren't left wondering if= their patch has broken SPDK, but we will be able to check in later on the = DPDK main periodic builds to see if the SPDK side is fixed, at which point = we can re-enable SPDK for per-patch testing.

Yes, please do.

--000000000000d3bbae0642b74157--