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 39B2E48A71; Mon, 3 Nov 2025 02:07:11 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0AD4F402B6; Mon, 3 Nov 2025 02:07:11 +0100 (CET) Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by mails.dpdk.org (Postfix) with ESMTP id B199740270 for ; Mon, 3 Nov 2025 02:07:09 +0100 (CET) Received: by mail-pl1-f172.google.com with SMTP id d9443c01a7336-29555b384acso13185805ad.1 for ; Sun, 02 Nov 2025 17:07:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1762132029; x=1762736829; 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=/5Co5N3x8pekugilinkAYLwIxv153xY8+e6RHELmc64=; b=gzh/9WzD277Stxys7oPya9Q5y647MMGDdMwetVBdFxVfGDZQ4UB5KZQPmJAjksIV4+ /Q6Jt1c7PWeQgRu1MVkoIUlX/px4lB4XCiOz6xdS1j/nMzrwZSTNsoSM/HyHGFy9jd51 7+nQcMqeqEibwfNb2ADNE94eeqLus/rjzDxa4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762132029; x=1762736829; 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=/5Co5N3x8pekugilinkAYLwIxv153xY8+e6RHELmc64=; b=rXaCAbEbhN8VcEPDUxNEJ3Vy0wo7nanjjaleBaIaPZjGp9JXG3n1/vQ0xBOHnnizFe eNw8FJlNFCPE/U07oJ4l+zNmi4o62O3xamqYcjkN0UBckpX5XfzsEM1nnJP2nuP9ZqDU E6De4/2CPFNyX+MovQfCpVW9lF/Aq7kWISx1L+ot8bQ4YAFckGt2k70CLMMMWHE3pYf7 EGNBErWNXC7ZE4uwro/7rBZ5duxlOAUu9E24KLDaNZcP0FFagk0qeCFBrX5j4ejQYrs4 WFwBKfqFsroOMbYuiyQLrx25beKuvbH2n8lmMS3mPRy52Z3heGbpnb1oq3jkDUDm4WyC C4fw== X-Forwarded-Encrypted: i=1; AJvYcCXXsP4m475TB5YKq6tcbdVzsULJooQo6TnF6XDhxcsMbjbdTX72D59SDXY7IBsFmvc94Q==@dpdk.org X-Gm-Message-State: AOJu0YyORn7utODk+ejoi+RrYtphPWRI3tJsSZgOdJIr4cqoXfH+xSeG Llhz5c+UQQB2Y5Yq470vGZWUr7xW71fcP8UmhYB4wsK6kiXKCb7T//f2bV6286e34vs+8u0GkWX 2fiZEGgX0OkNH8NcpWA9IZT6NqFXw5GvD/szr9taPug== X-Gm-Gg: ASbGncuIkV/GidwGP71gv60wZU7VDw+qU8zVZrG4hyq3JurFqxmmCyH3PrkYpfXJ1nS 0nNm881cdcOx3HzNMpSumomG7lDkxMoKTZwxF89P4OzazK98wfUjj8oPPkd5MnL9wpAiKGvLXYX 7ws8oq7vf7wgBVsvV05JTuB7aevY+l2Ih7/+Wv8NeoN4MfHtpCGU3tWJdW00Ghei8Ky1tnOHQN6 KVJfkKGbuzVnIVmRPOFxDs32eWEfRmn0WjQiYbf/IrtJdZsXg3M9Fa69b6dCDjYX2FDRED4iq6c JMggiiCTXFXXHRD6 X-Google-Smtp-Source: AGHT+IHXpUc2N6tyBq01hY0M9+/CNQwA9fGPgHfYbqFINVFbtgt6SbHAule/Zoiibyfxqx+XFK5MFj1tdLbnyjOw6S8= X-Received: by 2002:a17:903:f84:b0:295:523:691d with SMTP id d9443c01a7336-2951a5b960fmr155312275ad.46.1762132028739; Sun, 02 Nov 2025 17:07:08 -0800 (PST) MIME-Version: 1.0 References: <98CBD80474FA8B44BF855DF32C47DC35F6551F@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> From: Patrick Robb Date: Sun, 2 Nov 2025 20:06:05 -0500 X-Gm-Features: AWmQ_bmyN8DVxkI9Ay-NsgV5wYFKS347LVUKjAKqmOEEckeXag18S3MviDbg2J8 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="0000000000009eed7b0642a655bd" 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 --0000000000009eed7b0642a655bd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. > > --0000000000009eed7b0642a655bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Okay I'll push this change Monday morning.

On Sat, Nov 1, 2025 at 3:47=E2=80=AFAM Morten Br=C3=B8rup <mb@smartsharesystems.com> w= rote:
> 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 <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.

--0000000000009eed7b0642a655bd--