Hello,

I'm noting here that the compressdev test failures reported over the
weekend for the Community Lab are related to this, as the DTS compressdev
tests fail if EAL contains "failed." So, these patchseries failures can be
ignored by maintainers.

I see the fix from Hemant was merged by Thomas. It looks like some of the
recent failures are from series applied to next-net, so I'm guessing that
branch need to be rebased on main.

Thanks.

On Mon, Nov 11, 2024 at 4:36 AM Hemant Agrawal <hemant.agrawal@nxp.com>
wrote:

>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Monday, November 11, 2024 3:02 PM
> > To: Stephen Hemminger <stephen@networkplumber.org>; Gagandeep Singh
> > <G.Singh@nxp.com>; Sachin Saxena (OSS) <sachin.saxena@oss.nxp.com>;
> > Hemant Agrawal <hemant.agrawal@nxp.com>
> > Cc: dev@dpdk.org
> > Subject: Re: Bus scan is too chatty
> > Importance: High
> >
> > 10/11/2024 20:17, Stephen Hemminger:
> > > DPDK EAL needs to be less verbose for non-existent buses.
> > > Most users won't have embedded devices, and messages like:
> > >
> > > EAL: Scan for (fslmc) bus failed.
> > >
> > > will be confusing.
> >
> > When merging the recent fslmc patches, I've reduced the verbosity of some
> > fslmc logs appearing at the cleanup stage.
> >
> > This log is from EAL because fslmc scan fails.
> > It should not return an error if there is no bus or no environment
> variable.
> >
> > Sachin, Hemant, please could you fix it?
> >
> [Hemant] yes, let me have a look and provide a fix.
>