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

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Sat, Jul 18, 2026 at 01:02:01AM +0100, Mark Brown wrote:

> After merging the kunit-next tree, today's linux-next build
> (arm64 kunit) failed like this:

> [23:00:36] # gpio_unbind_with_consumers: ASSERTION FAILED at drivers/gpio/gpiolib-kunit.c:393
> [23:00:36] Expected ret == 0x0001, but
> [23:00:36]     ret == 0 (0x0)
> [23:00:36]     0x0001 == 1 (0x1)
> [23:00:36] [FAILED] gpio_unbind_with_consumers
> [23:00:36] # module: gpiolib_kunit

> This is caused by commit

>   a05cfd98c5eca (gpio: kunit: add test cases for software node hogs)

> which was from the gpio-brgl tree, it has only just become visible since 

>   34b5c0132952c (kunit: configs: enable GPIO kunit test cases in all_tests.config)

> was added causing the gpiolib tests to actually be run though neither of
> these commits was added today (the KUnit tree did not change for a
> while).  I'm not clear why this has started failing today, presumably
> some third commit from another tree has started triggering a regression
> since neither of these trees has changed.

> I have left this for today.

This issue has now reoccurred, the KUnit tree landed in mainline but
none of the gpiolib changes did including presumably whatever fix David
mentioned.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]