mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Linus Walleij <linusw@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	David Gow <david@davidgow.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: test failure after merge of the kunit-next tree
Date: Sat, 18 Jul 2026 01:02:01 +0100	[thread overview]
Message-ID: <alrCeerj_TmaqUuP@sirena.org.uk> (raw)

[-- 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 --]

                 reply	other threads:[~2026-07-18  0:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alrCeerj_TmaqUuP@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=david@davidgow.net \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox