From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [intel-lts:6.18/linux 1/1] unix_listen.c:26:10: fatal error: kselftest_harness.h: No such file or directory
Date: Tue, 08 Sep 2026 22:39:59 +0200 [thread overview]
Message-ID: <202609082248.MZqUA1cF-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
tree: https://github.com/intel/linux-intel-lts.git 6.18/linux
head: fba0f76dc652f3ae4d38d5a486cad998d353c67f
commit: 814c5b1590037330381a4ae83aaf40c0986ba2bb [1/1] selftests/net/af_unix: test listen() rejects wrong socket states
:::::: branch date: 6 days ago
:::::: commit date: 4 weeks ago
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260908/202609082248.MZqUA1cF-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260908/202609082248.MZqUA1cF-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/202609082248.MZqUA1cF-lkp@intel.com/
Note: the intel-lts/6.18/linux HEAD fba0f76dc652f3ae4d38d5a486cad998d353c67f builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> unix_listen.c:26:10: fatal error: kselftest_harness.h: No such file or directory
26 | #include "kselftest_harness.h"
| ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-08 20:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609082248.MZqUA1cF-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox