From: Mark Brown <broonie@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: KUnit failure after merge of the mm-nonmm-unstable tree
Date: Fri, 3 Jul 2026 15:43:35 +0100 [thread overview]
Message-ID: <akfKl6lJlGL6fPG3@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]
Hi all,
After merging the mm-nonmm-unstable tree, today's linux-next failed
KUnit testing like this:
[14:20:52] Configuring KUnit Kernel ...
[14:20:52] 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-
[14:21:06] 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
[14:22:11] ============================================================
[14:22:11] =================== cmdline (8 subtests) ===================
[14:22:11] # cmdline_test_memparse: EXPECTATION FAILED at lib/tests/cmdline_kunit.c:249
[14:22:11] Expected ret == e->result, but
[14:22:11] ret == -16 (0xfffffffffffffff0)
[14:22:11] e->result == -1 (0xffffffffffffffff)
[14:22:11] when parsing '0xffffffffffffffff0'
[14:22:11] [FAILED] cmdline_test_memparse
[14:22:11] # module: cmdline_kunit
[14:22:11] # cmdline: pass:7 fail:1 skip:0 total:8
[14:22:11] # Totals: pass:7 fail:1 skip:0 total:8
[14:22:11] ===================== [FAILED] cmdline =====================
[14:22:11] ============================================================
[14:22:11] Testing complete. Ran 9225 tests: passed: 9104, failed: 1, skipped: 120
[14:22:11] Failures: cmdline.cmdline_test_memparse
[14:22:11] Test results stored in /tmp/next/arm64_kunit.json
[14:22:11] Elapsed time: 79.318s total, 0.002s configuring, 14.632s building, 64.682s running
I honestly have no idea what's triggering this, nothing jumps out from
the commits introduced in the merge of the branch. If I have time later
I'll try to bisect the issue. I have used the tree from next-20260602
instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-03 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:43 Mark Brown [this message]
2026-07-03 16:39 ` linux-next: KUnit failure after merge of the mm-nonmm-unstable tree Mark Brown
2026-07-04 4:55 ` Alexey Dobriyan
2026-07-05 12:27 ` Mark Brown
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=akfKl6lJlGL6fPG3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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