From: "Liu, Yujie" <yujie.liu@intel.com>
To: lkp <lkp@intel.com>, "slyich@gmail.com" <slyich@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"Poimboe, Josh" <jpoimboe@redhat.com>
Subject: Re: make[5]: *** No rule to make target 'scripts/module.lds', needed by 'tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.ko'.
Date: Mon, 12 Jun 2023 05:36:21 +0000 [thread overview]
Message-ID: <8568e5e11983ea5da23206b6176760b1a9aee4b5.camel@intel.com> (raw)
In-Reply-To: <20230607224753.37df61df@nz>
Hi Sergei,
On Wed, 2023-06-07 at 22:47 +0100, Sergei Trofimovich wrote:
> On Thu, 8 Jun 2023 05:24:07 +0800
> kernel test robot <lkp@intel.com> wrote:
>
> > Hi Sergei,
> >
> > First bad commit (maybe != root cause):
> >
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head: a27648c742104a833a01c54becc24429898d85bf
> > commit: 82880283d7fcd0a1d20964a56d6d1a5cc0df0713 objtool: Fix
> > truncated string warning
> > date: 1 year, 4 months ago
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce:
> > #
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82880283d7fcd0a1d20964a56d6d1a5cc0df0713
> > git remote add linus
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > git fetch --no-tags linus master
> > git checkout 82880283d7fcd0a1d20964a56d6d1a5cc0df0713
> > make W=1 O=/tmp/kselftest headers
> > make W=1 O=/tmp/kselftest -C tools/testing/selftests
> > make W=1 O=/tmp/kselftest -C tools/testing/selftests/bpf
> >
> > 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/202306080543.EJWQZYkE-lkp@intel.com/
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > > > tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c:19:1:
> > > > warning: no previous prototype for 'bpf_testmod_test_mod_kfunc'
> > > > [-Wmissing-prototypes]
> > 19 | bpf_testmod_test_mod_kfunc(int i)
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> > > > tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c:24:14:
> > > > warning: no previous prototype for 'bpf_testmod_loop_test' [-
> > > > Wmissing-prototypes]
> > 24 | noinline int bpf_testmod_loop_test(int n)
> > | ^~~~~~~~~~~~~~~~~~~~~
> > > > tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c:36:30:
> > > > warning: no previous prototype for 'bpf_testmod_return_ptr' [-
> > > > Wmissing-prototypes]
> > 36 | __weak noinline struct file *bpf_testmod_return_ptr(int
> > arg)
> > | ^~~~~~~~~~~~~~~~~~~~~~
> > tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c:53:1:
> > warning: no previous prototype for 'bpf_testmod_test_read' [-
> > Wmissing-prototypes]
> > 53 | bpf_testmod_test_read(struct file *file, struct kobject
> > *kobj,
> > | ^~~~~~~~~~~~~~~~~~~~~
> > tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c:89:1:
> > warning: no previous prototype for 'bpf_testmod_test_write' [-
> > Wmissing-prototypes]
> > 89 | bpf_testmod_test_write(struct file *file, struct kobject
> > *kobj,
> > | ^~~~~~~~~~~~~~~~~~~~~~
> > --
> > > > make[5]: *** No rule to make target 'scripts/module.lds',
> > > > needed by
> > > > 'tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.ko'.
> > make[5]: Target '__modfinal' not remade because of errors.
>
> This failure looks unrelated to the commit it points to.
>
> lkp@, can you have a look at your bisection rules in a bit
> more of detail? There are at least 2 problems with this report:
>
> 1. the commit is 1.5 years old, it's unlikely you care about that old
> material
> 2. build failure might be an indication of a flaky build failure (or
> outright
> stale build tree)
>
> Both points have a chance of decreasing signal value from 0-DAY CI.
Really sorry for this false report. There was an environment issue in
the bot and caused a wrong bisection. We are working on fixing it.
Sorry again for the noise.
--
Best Regards,
Yujie
prev parent reply other threads:[~2023-06-12 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 21:24 kernel test robot
2023-06-07 21:47 ` Sergei Trofimovich
2023-06-12 5:36 ` Liu, Yujie [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=8568e5e11983ea5da23206b6176760b1a9aee4b5.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=slyich@gmail.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
all inboxes | Powered by JetHome®