Re: linux-next: test failure after merge of the landlock tree

["Mickaël Salaün" <mic@digikod.net>]

On Tue, Oct 20, 2026 at 10:54:29AM +0100, Mark Brown wrote:
> On Mon, Oct 19, 2026 at 11:11:20PM +0200, Mickaël Salaün wrote:
> > On Mon, Oct 19, 2026 at 07:17:09PM +0100, Mark Brown wrote:
> 
> > > This issue is still present today.
> 
> > I removed these wrong kunit checks Friday so it should be good now, but

In fact, I updated mic/next Wednesday with a new patch series addressing
these issues.  I only added two (unrelated) commits on top of that
Friday.

> > I notice that linux-next still has the next-20261001/landlock merge
> > commit instead of the latest changes from mic/next (which should not
> > conflict).  Could you please confirm that a normal merge works?
> 
> It was broken with whatever I fetched yesterday hence me reporting it
> still broken and merging the old version, I've just started the merge
> for today so I'll find out this afternoon if the fix worked.

The new commits from Wednesday don't add the bogus kunit lines (i.e.
there is no kunit_suppressed_warning_count() calls anymore), so it's not
possible to get the same error.

Merging mic/next into the current linux-next works for me, and
./tools/testing/kunit/kunit.py run --alltests works too.  Please let me
know if anything is wrong.

Regards,
 Mickaël