From: "Björn Töpel" <bjorn@kernel.org>
To: Ihor Solodrai <ihor.solodrai@pm.me>, andrii.nakryiko@gmail.com
Cc: bpf@vger.kernel.org, ast@kernel.org, eddyz87@gmail.com,
daniel@iogearbox.net, mykolal@fb.com,
Anders Roxell <anders.roxell@linaro.org>,
patchwork-bot+netdevbpf@kernel.org
Subject: Re: [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects
Date: Fri, 13 Sep 2024 16:51:49 +0200 [thread overview]
Message-ID: <877cbfwqre.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <172141323037.13293.5496223993427449959.git-patchwork-notify@kernel.org>
patchwork-bot+netdevbpf@kernel.org writes:
> Hello:
>
> This patch was applied to bpf/bpf-next.git (master)
> by Andrii Nakryiko <andrii@kernel.org>:
>
> On Thu, 18 Jul 2024 22:57:43 +0000 you wrote:
>> Make use of -M compiler options when building .test.o objects to
>> generate .d files and avoid re-building all tests every time.
>>
>> Previously, if a single test bpf program under selftests/bpf/progs/*.c
>> has changed, make would rebuild all the *.bpf.o, *.skel.h and *.test.o
>> objects, which is a lot of unnecessary work.
>>
>> [...]
>
> Here is the summary with links:
> - [bpf-next,v4] selftests/bpf: use auto-dependencies for test objects
> https://git.kernel.org/bpf/bpf-next/c/a3cc56cd2c20
I'm getting some build regressions for out-of-tree selftest build with
this patch on bpf-next/master. I'm building the selftests from the
selftest root, typically:
make O=/output/foo SKIP_TARGETS="" \
KSFT_INSTALL_PATH=/output/foo/kselftest \
-C tools/testing/selftests install
and then package the whole output kselftest directory, and use that to
populate the DUT.
Reverting this patch, resolves the issues.
Two issues:
1. The install target fails, resulting in many test scripts not copied
to the install directory (e.g. test_kmod.sh).
2. Building "all" target fails the second time.
To reproduce, do the following:
Pre-requisite
Build the kernel for yourfavorite arch -- my is RISC-V at moment ;-)
make O=/output/foo defconfig
make O=/output/foo kselftest-merge
make O=/output/foo
make O=/output/foo headers
1. Install fail
make O=/output/foo TARGETS=bpf SKIP_TARGETS="" \
KSFT_INSTALL_PATH=/output/foo/kselftest \
-C tools/testing/selftests install
2. Build "all" fails the second time
make O=/output/foo TARGETS=bpf SKIP_TARGETS="" \
KSFT_INSTALL_PATH=/output/foo/kselftest \
-C tools/testing/selftests
make O=/output/foo TARGETS=bpf SKIP_TARGETS="" \
KSFT_INSTALL_PATH=/output/foo/kselftest \
-C tools/testing/selftests
Any ideas on a workaround?
(And not related to this patch; It's annoying that "bpf" is the default
SKIP_TARGETS in kselftest. A bit meh 2024. ;-))
Björn
next prev parent reply other threads:[~2024-09-13 14:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 22:57 [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects Ihor Solodrai
2024-07-19 18:18 ` Andrii Nakryiko
2024-07-19 19:03 ` Ihor Solodrai
2024-07-19 21:54 ` Tony Ambardar
2024-07-19 22:25 ` Andrii Nakryiko
2024-07-19 23:21 ` [PATCH bpf-next v1] selftests/bpf: Fix wrong binary in Makefile log output Tony Ambardar
2024-07-20 0:14 ` bot+bpf-ci
2024-07-20 1:23 ` Eduard Zingerman
2024-07-20 2:57 ` Andrii Nakryiko
2024-07-20 5:23 ` Tony Ambardar
2024-07-23 1:35 ` Tony Ambardar
2024-07-23 1:37 ` Eduard Zingerman
2024-07-23 20:28 ` Andrii Nakryiko
2024-07-20 5:25 ` [PATCH bpf-next v2] " Tony Ambardar
2024-07-20 5:49 ` bot+bpf-ci
2024-07-22 15:17 ` bot+bpf-ci
2024-07-22 19:58 ` bot+bpf-ci
2024-07-23 1:40 ` bot+bpf-ci
2024-07-23 2:46 ` bot+bpf-ci
2024-07-23 20:30 ` patchwork-bot+netdevbpf
2024-07-19 18:20 ` [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects patchwork-bot+netdevbpf
2024-07-23 0:39 ` Alexei Starovoitov
2024-07-23 0:57 ` Eduard Zingerman
2024-07-23 1:49 ` Eduard Zingerman
2024-07-23 1:50 ` Ihor Solodrai
2024-07-23 19:25 ` Ihor Solodrai
2024-07-23 20:02 ` Andrii Nakryiko
2024-07-23 20:11 ` Ihor Solodrai
2024-09-13 14:51 ` Björn Töpel [this message]
2024-09-13 22:33 ` Ihor Solodrai
2024-09-14 10:54 ` Björn Töpel
2024-09-15 4:47 ` Ihor Solodrai
2024-09-15 15:41 ` Björn Töpel
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=877cbfwqre.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@pm.me \
--cc=mykolal@fb.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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