From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] Squash to "DO-NOT-MERGE: mptcp: improve code coverage for CI"
Date: Mon, 4 Nov 2024 13:07:56 +0100 [thread overview]
Message-ID: <21137b33-9b79-403a-8032-6aec174e91f2@kernel.org> (raw)
In-Reply-To: <26b229f0-9b4d-43ca-b06d-0d2ff1271c6c@kernel.org>
On 04/11/2024 12:58, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 04/11/2024 09:28, Geliang Tang wrote:
>> When our bpf_selftests are re-built, this error occurs:
>>
>> make[1]: *** No rule to make target 'atomics.lskel.h',
>> needed by '.../atomics.test.o'. Stop.
>> make[1]: *** Waiting for unfinished jobs....
>> make[1]: Leaving directory 'tools/testing/selftests/bpf'
>> make: *** [Makefile:259: install] Error 2
>> make: Leaving directory 'tools/testing/selftests'
>
> Ah yes, I already noticed that when checking some stuffs, but I didn't
> investigate. Thank you for having looked at this!
>
>> In this case, I had to remove the cache directory .virtme and recompile it
>> again. This was very time-consuming.
>
> You don't need to remove the whole ".virtme" directory, you can remove
> ".virtme/build*" instead, so you still have CCache (from ".virtme/ccache*").
>
>> A workaround patch for this is found in [1]. I don't know why this patch
>> has not been upstreamed, but it's in BPF CI environment. I think it's
>> necessary to synchronize this modification to MPTCP CI environment as well.
>
> It looks like another version has been applied in bpf-next, even if it
> is a fix:
>
> https://lore.kernel.org/bpf/20240916195919.1872371-2-ihor.solodrai@pm.me/
>
> Do you mind checking it please?
Just in case, their bpf-next/master branch has been rewritten in
between. The last ref I have is:
fd4a0e67838c ("selftests/bpf: Set vpath in Makefile to search for skels")
> If it works, I can backport it to our tree, and ask BPF maintainers if
> they can add these two patches in 'bpf' (fix) instead, because this
> issue is present in v6.12, but only fixed in next (v6.13).
>
> Cheers,
> Matt
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-11-04 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 8:28 [PATCH mptcp-next] Squash to "DO-NOT-MERGE: mptcp: improve code coverage for CI" Geliang Tang
2024-11-04 9:35 ` MPTCP CI
2024-11-04 11:58 ` Matthieu Baerts
2024-11-04 12:07 ` Matthieu Baerts [this message]
2024-11-05 10:04 ` Geliang Tang
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 16:39 Matthieu Baerts (NGI0)
2024-09-24 16:48 ` Matthieu Baerts
2024-09-24 17:36 ` MPTCP CI
2024-02-16 12:04 Matthieu Baerts (NGI0)
2024-02-16 20:21 ` Mat Martineau
2024-02-19 10:06 ` Matthieu Baerts
2024-02-19 10:35 ` Matthieu Baerts
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=21137b33-9b79-403a-8032-6aec174e91f2@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@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