All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>, oe-kbuild-all@lists.linux.dev
Subject: Re: [sj:damon/next 53/56] mm/damon/tests/vaddr-kunit.h:82:undefined reference to `kunit_try_catch_throw'
Date: Sun, 21 Jul 2024 09:06:33 -0700	[thread overview]
Message-ID: <20240721160633.357449-1-sj@kernel.org> (raw)
In-Reply-To: <202407212029.0FGR4ymI-lkp@intel.com>

Hello,

On Sun, 21 Jul 2024 21:09:06 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head:   c3004f235d68aa890660b532b04714a40abafd78
> commit: dfbce92b00bf8691cb86026352354792271c39f5 [53/56] mm/damon/tests: Rename test files to have _kunit suffix
> config: i386-randconfig-016-20240720 (https://download.01.org/0day-ci/archive/20240721/202407212029.0FGR4ymI-lkp@intel.com/config)
> compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240721/202407212029.0FGR4ymI-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/202407212029.0FGR4ymI-lkp@intel.com/
> 
> Note: the sj/damon/next HEAD c3004f235d68aa890660b532b04714a40abafd78 builds fine.
>       It only hurts bisectability.
> 
> All errors (new ones prefixed by >>):
> 
[...]
>    ld: mm/damon/vaddr.o: in function `damon_test_three_regions_in_vmas':
> >> mm/damon/tests/vaddr-kunit.h:82:(.text+0x106c): undefined reference to `kunit_try_catch_throw'
>    ld: mm/damon/tests/vaddr-kunit.h:86:(.text+0x11b7): undefined reference to `kunit_binary_assert_format'
[...]

Thank you for this report!  I think this is same to your previous report[1]
which I added a fix for that to the tree and replied the link to the fix?  So,
I guess there's no action item from my side.  Please let me know if I'm missing
something.

[1] https://lore.kernel.org/202407202132.JxTrdrIU-lkp@intel.com


Thanks,
SJ

      reply	other threads:[~2024-07-21 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 13:09 [sj:damon/next 53/56] mm/damon/tests/vaddr-kunit.h:82:undefined reference to `kunit_try_catch_throw' kernel test robot
2024-07-21 16:06 ` SeongJae Park [this message]

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=20240721160633.357449-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.