From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS
Date: Sun, 5 May 2024 22:44:19 +0800 [thread overview]
Message-ID: <202405052201.5beL5OYU-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240504044336.14411-1-jhubbard@nvidia.com>
References: <20240504044336.14411-1-jhubbard@nvidia.com>
TO: John Hubbard <jhubbard@nvidia.com>
TO: Shuah Khan <skhan@linuxfoundation.org>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
CC: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
CC: "Maciej Wieczor-Retman" <maciej.wieczor-retman@intel.com>
CC: Ryan Roberts <ryan.roberts@arm.com>
CC: Christian Brauner <brauner@kernel.org>
CC: Muhammad Usama Anjum <usama.anjum@collabora.com>
CC: Alexey Gladkov <legion@kernel.org>
CC: Valentin Obst <kernel@valentinobst.de>
CC: linux-kselftest@vger.kernel.org
CC: LKML <linux-kernel@vger.kernel.org>
CC: llvm@lists.linux.dev
CC: John Hubbard <jhubbard@nvidia.com>
Hi John,
kernel test robot noticed the following build errors:
[auto build test ERROR on ddb4c3f25b7b95df3d6932db0b379d768a6ebdf7]
url: https://github.com/intel-lab-lkp/linux/commits/John-Hubbard/selftests-fchmodat2-fix-clang-build-failure-due-to-static-libasan/20240504-124520
base: ddb4c3f25b7b95df3d6932db0b379d768a6ebdf7
patch link: https://lore.kernel.org/r/20240504044336.14411-1-jhubbard%40nvidia.com
patch subject: [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS
:::::: branch date: 34 hours ago
:::::: commit date: 34 hours ago
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240505/202405052201.5beL5OYU-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/r/202405052201.5beL5OYU-lkp@intel.com/
All errors (new ones prefixed by >>):
>> /usr/bin/x86_64-linux-gnu-ld: cannot find /opt/cross/clang-e6c3289804/lib/clang/18/lib/linux/libclang_rt.asan_static-x86_64.a: No such file or directory
>> /usr/bin/x86_64-linux-gnu-ld: cannot find /opt/cross/clang-e6c3289804/lib/clang/18/lib/linux/libclang_rt.asan-x86_64.a: No such file or directory
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-05-05 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 14:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-04 4:43 [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS John Hubbard
2024-05-07 7:45 ` Ryan Roberts
2024-05-07 16:19 ` John Hubbard
2024-05-07 16:34 ` Ryan Roberts
2024-05-07 16:47 ` John Hubbard
2024-05-07 16:56 ` Ryan Roberts
2024-05-10 11:52 ` Ryan Roberts
2024-05-10 17:56 ` John Hubbard
2024-05-10 18:22 ` John Hubbard
2024-05-11 17:19 ` Ryan Roberts
2024-05-30 3:58 ` Muhammad Usama Anjum
2024-05-30 4:35 ` John Hubbard
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=202405052201.5beL5OYU-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.