Re: [RFT] bootlinux: add bisection support

[Luis Chamberlain <mcgrof@kernel.org>]

On Wed, May 07, 2025 at 12:38:25PM +0200, Daniel Gomez wrote:
> On Mon, May 05, 2025 at 12:25:34PM +0100, Luis Chamberlain wrote:
> > On Fri, May 02, 2025 at 12:21:51AM +0200, Daniel Gomez wrote:
> > > However, I was trying to find a convenient way to loop in Ansible and I haven't
> > > been able to find one. I was thinking in:
> > 
> > Its the same chicken and egg problem with running fstests check for a long time,
> > and having a watchdog run to support a CI. We've now detatched the CI
> > stuff as part of the CI stuff, but similar questions came up long ago
> > when I tried to see if we could do both in one shot.
> 
> I see.
> 
> > 
> > What I ended up finding was the async ansible stuff but I never ended up
> > mucking with it:
> > 
> > https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_async.html
> >
> > Not sure if it helps here.
> > 
> > 
> >   Luis
> 
> I think the Ansible async task feature might be useful for step 4 (Wait until
> online), but it doesn't solve the overall problem.
> 
> Going back to the workflow proposal:
> 
> a. bisect-start target:
> 1. Ensures VM is booted
> 2. git bisect start
> 
> b. bisect-loop target:
> 1. Capture GRUB list and ask user for index
> 2. Build, install kernel
> 3. Reboot VM
> 4. Wait until online
> 4.a git bisect bad if timeout or other custom condition
> 4.b git bisect good if online (and if custom condition succeeds)
> 6. Shutdown vm (regarless of good/bad)
> 7. Reconfigure grub to boot from user option
> 8. Start VM and goto 2.
> 
> I think the CI loop approach suits better for this. What about something like
> this?
> 
> bisect:
> 	ansible-playbook bisect.yml --tags bisect-init
> 	while ! [ -f .bisect-loop-finished ]; do \
> 		ansible-playbook bisect.yml
> 	done

Looks good!

  Luis