From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
kdevops@lists.linux.dev
Subject: Re: [RFT] bootlinux: add bisection support
Date: Mon, 5 May 2025 12:25:34 -0700 [thread overview]
Message-ID: <aBkQrtP_nLt8kAtm@bombadil.infradead.org> (raw)
In-Reply-To: <lst4kgiv57cvjd3afijad7khy63knww7dhsr7lwn2kcftcwcp5@jjsmjq46ggec>
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.
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
next prev parent reply other threads:[~2025-05-05 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 0:09 [RFT] bootlinux: add bisection support Luis Chamberlain
2025-04-24 5:47 ` Luis Chamberlain
2025-04-24 6:40 ` Daniel Gomez
2025-04-24 7:25 ` Daniel Gomez
2025-04-24 13:36 ` Daniel Gomez
2025-04-24 17:10 ` Luis Chamberlain
2025-04-24 18:37 ` Daniel Gomez
2025-04-24 17:08 ` Luis Chamberlain
2025-04-24 17:12 ` Luis Chamberlain
2025-04-24 18:41 ` Daniel Gomez
2025-05-01 22:21 ` Daniel Gomez
2025-05-05 19:25 ` Luis Chamberlain [this message]
2025-05-07 10:38 ` Daniel Gomez
2025-05-07 18:52 ` Luis Chamberlain
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=aBkQrtP_nLt8kAtm@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@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