Disable SPDK testing again?

[Morten Brørup]

> From: David Marchand [mailto:david.marchand at redhat.com]
> Sent: Friday, 31 October 2025 10.18
> 
> On Fri, 31 Oct 2025 at 10:11, Morten Brørup <mb at smartsharesystems.com>
> wrote:
>  > While it is just a warning in the CI dashboard, I don't think we
> > > should waste resources on this testing.
> > > Opinions?
> >
> > We should ask ourselves why they are doing that.
> > Is something wrong (or incomplete) with our handling of -
> Denable_libs?
> > Are we including unnecessary optional libs?
> >
> > It seems like they are using -Ddisable_libs, not -Denable_libs. Don't
> they know about -Denable_libs?
> 
> I reached out to some SPDK dev when I was working on enable_libs.
> I also Cc: one of them on the patches but never got a reply.

@Bruce, the SPDK patch [1] was signed off by Tomasz Zawadzki <tomasz.zawadzki at intel.com>; maybe you could try reaching out through internal Intel channels and educate him about -Denable_libs.

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?

[1]: https://github.com/spdk/dpdk/commit/74b1a804eda2ed99d1ecaae5b79de7df6d74e8ff