public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"David Gow" <davidgow@google.com>,
	johannes.berg@intel.com
Cc: shuah <shuah@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	Networking <netdev@vger.kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Error during building on next-20250926 - kunit.py run --alltests run
Date: Sun, 28 Sep 2025 15:22:11 -0600	[thread overview]
Message-ID: <6e0d5120-868c-45fd-9ec5-67764a257ab5@linuxfoundation.org> (raw)
In-Reply-To: <47b370c2-9ab2-419f-9d43-8da310fedb4a@linuxfoundation.org>

On 9/28/25 15:11, Shuah Khan wrote:
> Hi Thomas and David,
> 
> I am seeing the following error during "kunit.py run --alltests run"
> next-20250926.
> 
> $ make all compile_commands.json scripts_gdb ARCH=um O=.kunit --jobs=16
> ERROR:root:/usr/bin/ld: drivers/net/wireless/intel/iwlwifi/tests/devinfo.o: in function `devinfo_pci_ids_config':
> devinfo.c:(.text+0x2d): undefined reference to `iwl_bz_mac_cfg'
> collect2: error: ld returned 1 exit status
> make[3]: *** [../scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
> make[2]: *** [/linux/linux_next/Makefile:1242: vmlinux] Error 2
> make[1]: *** [/linux/linux_next/Makefile:248: __sub-make] Error 2
> make: *** [Makefile:248: __sub-make] Error 2

Same problem when running - kunit.py run --alltests --arch x86_64
> 
> Possile intearction between these two commits: Note: linux-kselftext
> kunit branch is fine I am going send kunit pr to Linus later today.
> Heads up that "kunit.py run --alltests run" is failing on next-20250926
> 
> 
> commit 031cdd3bc3f369553933c1b0f4cb18000162c8ff
> Author: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> Date:   Mon Sep 8 09:03:38 2025 +0200
> 
>      kunit: Enable PCI on UML without triggering WARN()
> 
> 
> commit 137b0bb916f1addb2ffbefd09a6e3e9d15fe6100
> Author: Johannes Berg <johannes.berg@intel.com>
> Date:   Mon Sep 15 11:34:28 2025 +0300
> 
>      wifi: iwlwifi: tests: check listed PCI IDs have configs
> 
> Note: linux-kselftext build just fine.

linux-kselftect kunit branch is fine.

thanks,
-- Shuah

  reply	other threads:[~2025-09-28 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 21:11 Error during building on next-20250926 - kunit.py run --alltests run Shuah Khan
2025-09-28 21:22 ` Shuah Khan [this message]
2025-09-29  7:07   ` Berg, Johannes
2025-09-29 16:05     ` Shuah Khan
2025-09-29 16:07       ` Shuah Khan

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=6e0d5120-868c-45fd-9ec5-67764a257ab5@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=davidgow@google.com \
    --cc=johannes.berg@intel.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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