public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Mark Brown <broonie@kernel•org>
To: Catalin Marinas <catalin.marinas@arm•com>,
	Will Deacon <will@kernel•org>, Ard Biesheuvel <ardb@kernel•org>,
	Kevin Brodsky <kevin.brodsky@arm•com>
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 arm64 tree
Date: Wed, 3 Jun 2026 12:24:36 +0100	[thread overview]
Message-ID: <aiAO9KcQ8Irve7od@sirena.org.uk> (raw)

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

Hi all,

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

[11:04:45] Configuring KUnit Kernel ...
[11:04:45] 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-
[11:05:11] 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
Command '['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']' timed out after 300 seconds
[11:10:11] [FAILED] <missing>
[11:10:11] Testing complete. Ran 0 tests: errors: 1
[11:10:11] Test results stored in /tmp/next/arm64_kunit.json
[11:10:11] Elapsed time: 325.499s total, 0.002s configuring, 25.490s building, 300.006s running

which is not hugely informative.  Looking at what's new in the arm64
tree from yesterday I'd be astonished if this were anything other than
Ard's linear map series.  

This is running on a Graviton 4 system, the kunit command line is:

./tools/testing/kunit/kunit.py run --failed --alltests --kconfig_add CONFIG_KASAN=y --arch arm64 --cross_compile=aarch64-linux-gnu-

I have used the version from next-20260602 instead.

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

                 reply	other threads:[~2026-06-03 11:24 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=aiAO9KcQ8Irve7od@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=ardb@kernel$(echo .)org \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=kevin.brodsky@arm$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox