From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Tejun Heo <tj@kernel.org>, Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Alexei Starovoitov <ast@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: selftests/sched_ext: testing on BPF CI
Date: Fri, 2 May 2025 14:40:45 -0700 [thread overview]
Message-ID: <0a039ded-b67d-4a0c-a851-e3aafff57321@linux.dev> (raw)
In-Reply-To: <3fb44500b87b0f1d8360bc7a1f3ae972d3c5282f@linux.dev>
On 2025-01-28 4:21 p.m., Ihor Solodrai wrote:
> Hi Tejun, Andrea.
>
> I tested a couple of variants of bpf-next + sched_ext source tree,
> just sharing the results.
>
> I found a working state: BPF CI pipeline ran successfully twice
> (that's 8 build + run of selftests/sched_ext/runner in total).
>
> Working state requires most patches between sched_ext/master and
> sched_ext/for-6.14-fixes [1], and also the patch
> "tools/sched_ext: Receive updates from SCX repo" [2]
>
> On plain bpf-next the dsp_local_on test fails [3].
> Without the patch [2] there is a build error [4]: missing
> SCX_ENUM_INIT definition.
>
> We probably don't want to enable selftests/sched_ext on BPF CI with
> that many "temporary" patches. I suggest to wait until all of this is
> merged upstream.
>
Hi everyone. I tried enabling sched_ext selftests on CI today, and there
are no issues on bpf-next tip (f263336a41da).
https://github.com/kernel-patches/vmtest/actions/runs/14802453691
If there are no objections, I'm going to push this to BPF CI on Monday.
As a reminder, this means that selftests/sched_ext test runner will be
built and executed for pending BPF patches, and BPF CI pipeline will
fail in case of problems there.
> You can check the full list of patches here:
> https://github.com/kernel-patches/vmtest/pull/332/files
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/log/?h=for-6.14-fixes
> [2] https://lore.kernel.org/all/Z1ucTqJP8IeIXZql@slm.duckdns.org/
> [3] https://github.com/kernel-patches/vmtest/actions/runs/13019837022
> [4] https://github.com/kernel-patches/vmtest/actions/runs/13020458479
next prev parent reply other threads:[~2025-05-02 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 0:21 selftests/sched_ext: testing on BPF CI Ihor Solodrai
2025-01-29 7:27 ` Andrea Righi
2025-01-29 16:19 ` Tejun Heo
2025-05-02 21:40 ` Ihor Solodrai [this message]
2025-05-03 5:41 ` Andrea Righi
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=0a039ded-b67d-4a0c-a851-e3aafff57321@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.