public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Brian Norris <briannorris@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Tsai Sung-Fu <danielsftsai@google.com>,
	linux-kernel@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v3] genirq: Add kunit tests for depth counts
Date: Sun, 18 May 2025 00:13:47 +0800	[thread overview]
Message-ID: <202505172307.yTjulMhx-lkp@intel.com> (raw)
In-Reply-To: <20250516183213.848182-1-briannorris@chromium.org>

Hi Brian,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/irq/core]
[also build test ERROR on next-20250516]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Brian-Norris/genirq-Add-kunit-tests-for-depth-counts/20250517-023519
base:   tip/irq/core
patch link:    https://lore.kernel.org/r/20250516183213.848182-1-briannorris%40chromium.org
patch subject: [PATCH v3] genirq: Add kunit tests for depth counts
config: arm64-randconfig-001-20250517 (https://download.01.org/0day-ci/archive/20250517/202505172307.yTjulMhx-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250517/202505172307.yTjulMhx-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505172307.yTjulMhx-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: undefined symbol: kunit_binary_ptr_assert_format
   >>> referenced by irq_test.c:54 (kernel/irq/irq_test.c:54)
   >>>               kernel/irq/irq_test.o:(irq_disable_depth_test) in archive vmlinux.a
   >>> referenced by irq_test.c:54 (kernel/irq/irq_test.c:54)
   >>>               kernel/irq/irq_test.o:(irq_disable_depth_test) in archive vmlinux.a
   >>> referenced by irq_test.c:81 (kernel/irq/irq_test.c:81)
   >>>               kernel/irq/irq_test.o:(irq_free_disabled_test) in archive vmlinux.a
   >>> referenced 5 more times
--
>> ld.lld: error: undefined symbol: kunit_try_catch_throw
   >>> referenced by irq_test.c:0 (kernel/irq/irq_test.c:0)
   >>>               kernel/irq/irq_test.o:(irq_cpuhotplug_test) in archive vmlinux.a

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2025-05-17 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 18:30 [PATCH v3] genirq: Add kunit tests for depth counts Brian Norris
2025-05-17 16:13 ` kernel test robot [this message]
2025-05-19 22:59   ` Brian Norris

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=202505172307.yTjulMhx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=briannorris@chromium.org \
    --cc=danielsftsai@google.com \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@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