Re: Meeting proposal for KernelCI Bisection

Hi Ben,

On 04/03/2026 6:28 pm, Ben Copeland wrote:
> Hello all,
> 
> On the KernelCI roadmap, I propose we start a discussion on adding
> Automated Bisection into KernelCI.
> 
> We have many options and have learnt many lessons from past
> experiences. KernelCI today lacks the ability to do automated
> bisection. So I would like to put the meeting together to cover
> 
>   - What bisection in Kernelci should look like
>   - How do we go about Bisection at an efficient computational cost
>   - What are the options for automation
>   - Put together actions list
> 
> Bisection needs to fit into KernelCI V2 tooling (i.e., Kubernetes,
> kci-dev). We also want to provide bisected results to the Maestro
> mailing list.
> 
> I have a list of people to include on a call. If you are interested,
> please let me know, and I will add you to the meeting.
> 
> I propose the meeting for Thursday, 19 March, at 15:00 UTC.

Many thanks for starting this thread.  I'm available to join the
meeting and I would be happy to collaborate on this topic.

As some of you already know, I've independently made an automated
bisection PoC[1] based on the lessons learnt from previous KernelCI
implementations and community feedback.  This addresses several key
issues that have been identified over the years.  I'm now working on
a first stable release and a roadmap with extra features.  I can
prepare a breakdown of how this may apply to KernelCI as it currently
stands ahead of the meeting.

I believe this is related but not quite the same use case as enabling
developers to run bisections locally while accessing hardware remote
labs, which would seem like where kci-dev would help.  I'd be good if
we could share some logic with a common library if applicable and
coordinate these various efforts as much as we can in general.

Best wishes,
Guillaume

[1] https://gtucker.io/posts/2026-02-02-vixi-and-renelick/