From mb at smartsharesystems.com Sat Nov 1 08:47:11 2025 From: mb at smartsharesystems.com (=?UTF-8?B?TW9ydGVuIEJyw7hydXA=?=) Date: Sat, 1 Nov 2025 08:47:11 +0100 Subject: Disable SPDK testing again? In-Reply-To: References: <98CBD80474FA8B44BF855DF32C47DC35F6551F@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> > From: Patrick Robb [mailto:probb at iol.unh.edu] > Sent: Friday, 31 October 2025 16.13 > > On Fri, Oct 31, 2025 at 6:02?AM Morten Br?rup 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. From probb at iol.unh.edu Mon Nov 3 02:06:05 2025 From: probb at iol.unh.edu (Patrick Robb) Date: Sun, 2 Nov 2025 20:06:05 -0500 Subject: Disable SPDK testing again? In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> References: <98CBD80474FA8B44BF855DF32C47DC35F6551F@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65520@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk> Message-ID: Okay I'll push this change Monday morning. On Sat, Nov 1, 2025 at 3:47?AM Morten Br?rup wrote: > > From: Patrick Robb [mailto:probb at iol.unh.edu] > > Sent: Friday, 31 October 2025 16.13 > > > > On Fri, Oct 31, 2025 at 6:02?AM Morten Br?rup > 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: