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 57E4848A46; Fri, 31 Oct 2025 16:14:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5324640395; Fri, 31 Oct 2025 16:14:06 +0100 (CET) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by mails.dpdk.org (Postfix) with ESMTP id 3B1EB40150 for ; Fri, 31 Oct 2025 16:14:04 +0100 (CET) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-7a74b13f4f8so1435629b3a.1 for ; Fri, 31 Oct 2025 08:14:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1761923643; x=1762528443; 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=4g3T8UzFlTMpCrC35gpq6X6scEqhc7FALyGLFt2jz7A=; b=PrXobmpsZBQkRF7Ak6xcoyg3GinxVpPTKNtRez1MWwhRArgTIEzqlpugOnV944HdsC jyk7Tg3gnKJxOe7ilzz5LmQgQonIhe9OZ6KS9f6t+M6Rht4QALmrd+WF4RR7b/glkIPd Ps2PJJMHqZtqidnSItdgRivnO9LQ6FcV00vYQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761923643; x=1762528443; 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=4g3T8UzFlTMpCrC35gpq6X6scEqhc7FALyGLFt2jz7A=; b=UEhcJEowJ+OMGUSv58Bid+2TtTbJx0LI8qvpQr5FbNBMOlzp6n7IkMdvFsiCxhjWf7 9XMc/6e0XZs99X0qYjTT7SCZnHOYwy/QWTD8reTvYVs7snOuH9X7hQU2Rq3DmqB3GhHh IdF40rPQNMZvSpTN1xz0u7yO3gbrUxC2wRmkzmZJLZOQmWsWzKKm0ZPxnHg1B5qQVUQH kU+Ykyk9D1Y8w0NoWEJ4DJiXxiTdHgLumdzUDinMFQSgGHkVlmeppbj39IVkVl3wOy8F CBJpVrGWAITawo4bXmnQg7XAQWaJUDx9xbk+BRD+p/4yq/ogGSSr/Z4lFrWyXqOHXtOB BxvA== X-Forwarded-Encrypted: i=1; AJvYcCUcbZqj8wgMxAJtYS5i/JW2FQBU7V7yZo5Fq/BSWMMV9w3h+hD1lkHFBbdznbpxIueEDA==@dpdk.org X-Gm-Message-State: AOJu0YxtAGaqmf83H7G/gooin93SWEFtgGdQNYO74v3H6Z1brSlgOQAX pdZmO/i3KyrLAIFxeF+qWBmFfLUt91nGdA9e05OpMXUcFstZTsfSsiPLAO9LpQaSkRQSeD7JN5e gPuUal7/WmdglVgd1Dq8RhoUM5XieV+27z2nuEP1+Dw== X-Gm-Gg: ASbGncsv7lD+oIhGizN+JRfkxmS+pTU/inbCr6b86JUTP/ZPkFiaRt6gcbexCAJvAcW g0IIRU57kSwXBcUR1rTPGoAAnl6tGJ+ywsNXLNBDpnKxwsTdIEO7k6QOU4uuOCrZAZcRJaiR8Th SQf5rgu0xwj4pg2Y2PgkDJKS2ePMn2pd96yqZgLay1nx5URYvcohEjDKJ6uxEMg+8SCj1i9vMKe qq3kF6HZjlzpovk4INzI2/yG7Dq8naLiH52WJ0ymOxs7+E9BEiRIzkLw03DbZR6HLHJrAkO0DuG 7KmUfABV7THgdTj/bQ== X-Google-Smtp-Source: AGHT+IHsd9csprSugW7KlQcLhFxTW5tqsClstFSG3lm1hhq8NZgRt/fL6J6IPYxc22wlbw+lZax/zrIP8YrU+id/Oa0= X-Received: by 2002:a17:902:e78d:b0:271:479d:3de2 with SMTP id d9443c01a7336-2951a3d0b37mr59237025ad.13.1761923642999; Fri, 31 Oct 2025 08:14:02 -0700 (PDT) MIME-Version: 1.0 References: <98CBD80474FA8B44BF855DF32C47DC35F6551F@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> From: Patrick Robb Date: Fri, 31 Oct 2025 11:13:01 -0400 X-Gm-Features: AWmQ_blvxGNh-AlBdRlpbkFiUPpd6UIowrvDk1CupgTR2CYUIkWUoUPdnijdLA0 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="000000000000dcd8da064275d0ca" 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 --000000000000dcd8da064275d0ca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. --000000000000dcd8da064275d0ca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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 notice when th= ey fix it, so we can enable SPDK testing again?

One option=C2=A0is I can disable SPDK testing for the "pe= r-patch" testing, but leave it enabled for the periodic (once per 48 h= ours) runs on DPDK main. That way patch submitters aren't left wonderin= g 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 po= int we can re-enable SPDK for per-patch testing.
--000000000000dcd8da064275d0ca--