From: kernel test robot <lkp@intel.com>
To: Lina Wang <lina.wang@mediatek.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Maciej enczykowski <maze@google.com>
Subject: error: unable to open output file 'kselftest/net/bpf/nat6to4.o': 'No such file or directory'
Date: Tue, 2 Aug 2022 01:47:24 +0800 [thread overview]
Message-ID: <202208020112.9k23Y19d-lkp@intel.com> (raw)
Hi Lina,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0fac198def2b41138850867b6aa92044c76ff802
commit: edae34a3ed9293b5077dddf9e51a3d86c95dc76a selftests net: add UDP GRO fraglist + bpf self-tests
date: 3 months ago
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=edae34a3ed9293b5077dddf9e51a3d86c95dc76a
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout edae34a3ed9293b5077dddf9e51a3d86c95dc76a
make O=/tmp/kselftest headers
make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> error: unable to open output file 'kselftest/net/bpf/nat6to4.o': 'No such file or directory'
1 error generated.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-08-01 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 17:47 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-19 14:27 error: unable to open output file 'kselftest/net/bpf/nat6to4.o': '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=202208020112.9k23Y19d-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=lina.wang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@google.com \
/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