From: Patrick Robb <probb@iol.unh.edu>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: David Marchand <david.marchand@redhat.com>,
bruce.richardson@intel.com, Aaron Conole <aconole@redhat.com>,
dpdk-techboard <techboard@dpdk.org>,
ci@dpdk.org, dev <dev@dpdk.org>
Subject: Re: Disable SPDK testing again?
Date: Sun, 2 Nov 2025 20:06:05 -0500 [thread overview]
Message-ID: <CAJvnSUCH2U5DgpkRXJEX1yJmpE1yhM6KHEE9_8Z8xghW52Tg9Q@mail.gmail.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65526@smartserver.smartshare.dk>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Okay I'll push this change Monday morning.
On Sat, Nov 1, 2025 at 3:47 AM Morten Brørup <mb@smartsharesystems.com>
wrote:
> > From: Patrick Robb [mailto:probb@iol.unh.edu]
> > Sent: Friday, 31 October 2025 16.13
> >
> > On Fri, Oct 31, 2025 at 6:02 AM Morten Brørup <mb@smartsharesystems.com>
> 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.
>
>
[-- Attachment #2: Type: text/html, Size: 1379 bytes --]
prev parent reply other threads:[~2025-11-03 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 8:38 David Marchand
2025-10-31 9:11 ` Morten Brørup
2025-10-31 9:17 ` David Marchand
2025-10-31 10:02 ` Morten Brørup
2025-10-31 15:13 ` Patrick Robb
2025-11-01 7:47 ` Morten Brørup
2025-11-03 1:06 ` Patrick Robb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJvnSUCH2U5DgpkRXJEX1yJmpE1yhM6KHEE9_8Z8xghW52Tg9Q@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=techboard@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).