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

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

[Mark Brown]

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

Hi all,

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

[22:59:27] Configuring KUnit Kernel ...
[22:59:27] Building KUnit Kernel ...
Populating config with:
$ make ARCH=arm64 O=/tmp/next/arm64_kunit olddefconfig CROSS_COMPILE=aarch64-linux-gnu-
Building with:
$ make all compile_commands.json scripts_gdb ARCH=arm64 O=/tmp/next/arm64_kunit --jobs=192 CROSS_COMPILE=aarch64-linux-gnu-
[22:59:30] Starting KUnit Kernel (1/1)...
Running tests with:
$ qemu-system-aarch64 -nodefaults -m 1024 -kernel /tmp/next/arm64_kunit/arch/arm64/boot/Image.gz -append 'kunit.enable=1 console=ttyAMA0 kunit_shutdown=reboot' -no-reboot -nographic -accel kvm -accel hvf -accel tcg -serial stdio -machine virt -cpu max
[23:00:36] ============================================================
[23:00:36] ========== gpio-unbind-with-consumers (1 subtest) ==========
[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
[23:00:36] =========== [FAILED] gpio-unbind-with-consumers ============
[23:00:36] # gpio-swnode-hog:     # failed to initialize (-17)
[23:00:36] [FAILED] gpio-swnode-hog
[23:00:36] ============================================================
[23:00:36] Testing complete. Ran 9377 tests: passed: 9284, failed: 2, skipped: 91
[23:00:36] Failures: gpio-unbind-with-consumers, gpio-swnode-hog
[23:00:36] Test results stored in /tmp/next/arm64_kunit.json
[23:00:36] Elapsed time: 69.716s total, 0.002s configuring, 3.680s building, 66.027s running

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.

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

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

[David Gow]

Le 18/07/2026 à 08:02, Mark Brown a écrit :
> Hi all,
> 
> After merging the kunit-next tree, today's linux-next build
> (arm64 kunit) failed like this:
> 
> [22:59:27] Configuring KUnit Kernel ...
> [22:59:27] Building KUnit Kernel ...
> Populating config with:
> $ make ARCH=arm64 O=/tmp/next/arm64_kunit olddefconfig CROSS_COMPILE=aarch64-linux-gnu-
> Building with:
> $ make all compile_commands.json scripts_gdb ARCH=arm64 O=/tmp/next/arm64_kunit --jobs=192 CROSS_COMPILE=aarch64-linux-gnu-
> [22:59:30] Starting KUnit Kernel (1/1)...
> Running tests with:
> $ qemu-system-aarch64 -nodefaults -m 1024 -kernel /tmp/next/arm64_kunit/arch/arm64/boot/Image.gz -append 'kunit.enable=1 console=ttyAMA0 kunit_shutdown=reboot' -no-reboot -nographic -accel kvm -accel hvf -accel tcg -serial stdio -machine virt -cpu max
> [23:00:36] ============================================================
> [23:00:36] ========== gpio-unbind-with-consumers (1 subtest) ==========
> [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
> [23:00:36] =========== [FAILED] gpio-unbind-with-consumers ============
> [23:00:36] # gpio-swnode-hog:     # failed to initialize (-17)
> [23:00:36] [FAILED] gpio-swnode-hog
> [23:00:36] ============================================================
> [23:00:36] Testing complete. Ran 9377 tests: passed: 9284, failed: 2, skipped: 91
> [23:00:36] Failures: gpio-unbind-with-consumers, gpio-swnode-hog
> [23:00:36] Test results stored in /tmp/next/arm64_kunit.json
> [23:00:36] Elapsed time: 69.716s total, 0.002s configuring, 3.680s building, 66.027s running
> 
> 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.


I'm pretty sure the fix for this is a part of:
gpio: kunit: add test cases verifying swnode devlink support
(https://lore.kernel.org/all/20260720-swnode-fw-devlink-v5-1-ec250ae6af91@oss.qualcomm.com/#r)

-- David

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

[Shuah Khan]

On 7/20/26 03:01, David Gow wrote:
> Le 18/07/2026 à 08:02, Mark Brown a écrit :
>> Hi all,
>>
>> After merging the kunit-next tree, today's linux-next build
>> (arm64 kunit) failed like this:
>>
>> [22:59:27] Configuring KUnit Kernel ...
>> [22:59:27] Building KUnit Kernel ...
>> Populating config with:
>> $ make ARCH=arm64 O=/tmp/next/arm64_kunit olddefconfig CROSS_COMPILE=aarch64-linux-gnu-
>> Building with:
>> $ make all compile_commands.json scripts_gdb ARCH=arm64 O=/tmp/next/arm64_kunit --jobs=192 CROSS_COMPILE=aarch64-linux-gnu-
>> [22:59:30] Starting KUnit Kernel (1/1)...
>> Running tests with:
>> $ qemu-system-aarch64 -nodefaults -m 1024 -kernel /tmp/next/arm64_kunit/arch/arm64/boot/Image.gz -append 'kunit.enable=1 console=ttyAMA0 kunit_shutdown=reboot' -no-reboot -nographic -accel kvm -accel hvf -accel tcg -serial stdio -machine virt -cpu max
>> [23:00:36] ============================================================
>> [23:00:36] ========== gpio-unbind-with-consumers (1 subtest) ==========
>> [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
>> [23:00:36] =========== [FAILED] gpio-unbind-with-consumers ============
>> [23:00:36] # gpio-swnode-hog:     # failed to initialize (-17)
>> [23:00:36] [FAILED] gpio-swnode-hog
>> [23:00:36] ============================================================
>> [23:00:36] Testing complete. Ran 9377 tests: passed: 9284, failed: 2, skipped: 91
>> [23:00:36] Failures: gpio-unbind-with-consumers, gpio-swnode-hog
>> [23:00:36] Test results stored in /tmp/next/arm64_kunit.json
>> [23:00:36] Elapsed time: 69.716s total, 0.002s configuring, 3.680s building, 66.027s running
>>
>> 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.
> 
> 
> I'm pretty sure the fix for this is a part of:
> gpio: kunit: add test cases verifying swnode devlink support
> (https://lore.kernel.org/all/20260720-swnode-fw-devlink-v5-1-ec250ae6af91@oss.qualcomm.com/#r)
> 

Thanks David.

Hope this makes it into linux-next soon through gpio tree.

thanks,
-- Shuah

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

[Mark Brown]

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

On Tue, Jul 21, 2026 at 08:41:29AM -0600, Shuah Khan wrote:
> On 7/20/26 03:01, David Gow wrote:

> > I'm pretty sure the fix for this is a part of:
> > gpio: kunit: add test cases verifying swnode devlink support
> > (https://lore.kernel.org/all/20260720-swnode-fw-devlink-v5-1-ec250ae6af91@oss.qualcomm.com/#r)

> Thanks David.

> Hope this makes it into linux-next soon through gpio tree.

Whatever it was the problem went away yesterday, though sometimes that
is just glitchy tests.

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