From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: Ihor Solodrai <ihor.solodrai@linux.dev>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Alexei Starovoitov <ast@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: selftests/sched_ext: testing on BPF CI
Date: Wed, 29 Jan 2025 06:19:27 -1000 [thread overview]
Message-ID: <Z5pVD-c9f7TmS1rA@slm.duckdns.org> (raw)
In-Reply-To: <Z5nYRj1L4h1KCWE1@gpd3>
On Wed, Jan 29, 2025 at 08:27:02AM +0100, Andrea Righi wrote:
> Hi Ihor,
>
> On Wed, Jan 29, 2025 at 12:21:43AM +0000, Ihor Solodrai wrote:
> > Hi Tejun, Andrea.
> >
> > I tested a couple of variants of bpf-next + sched_ext source tree,
> > just sharing the results.
>
> Thanks for testing!
>
> >
> > I found a working state: BPF CI pipeline ran successfully twice
> > (that's 8 build + run of selftests/sched_ext/runner in total).
>
> Ok.
>
> >
> > 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 definitely need all the patches in sched_ext/for-6.14-fixes. I think
> once Tejun sends the PR and we land the for-6.14-fixes upstream we should
> reach a stable state with the sched_ext selftests. I don't have any other
> additional pending fix at the moment.
>
> >
> > 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.
>
> Sounds reasonable to me. Tejun?
Sure.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-01-29 16:19 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 [this message]
2025-05-02 21:40 ` Ihor Solodrai
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=Z5pVD-c9f7TmS1rA@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.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