From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: /bin/bash: line 1: tools/bpf/bpftool/bpftool: No such file or directory
Date: Sun, 03 May 2026 04:32:44 +0200 [thread overview]
Message-ID: <202605030403.FrjvXYyE-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Blaise-Boscaccy/crypto-pkcs7-add-flag-for-validated-trust-on-a-signed-info-block/20260502-054022
head: dd83740fb7ac14161725928d746e1715974802da
commit: a89290bb17ae209a158be7be88616bce4b03e431 selftests/hornet: Add a selftest for the Hornet LSM
date: 29 hours ago
:::::: branch date: 29 hours ago
:::::: commit date: 29 hours ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260503/202605030403.FrjvXYyE-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260503/202605030403.FrjvXYyE-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/202605030403.FrjvXYyE-lkp@intel.com/
All errors (new ones prefixed by >>):
>> /bin/bash: line 1: tools/bpf/bpftool/bpftool: No such file or directory
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-03 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 2:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-11 14:06 /bin/bash: line 1: tools/bpf/bpftool/bpftool: No such file or directory kernel test robot
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=202605030403.FrjvXYyE-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.