public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>, kdevops@lists.linux.dev
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH 1/2] ansible.cfg: Enable the Ansible debugger when a task fails
Date: Wed, 16 Jul 2025 14:38:41 -0400	[thread overview]
Message-ID: <289d8634-176c-4788-bb01-8e5ffa5e421d@kernel.org> (raw)
In-Reply-To: <a828c6f4-339a-4fca-b2a4-6219d2a28bc5@kernel.org>

On 7/16/25 1:44 PM, Daniel Gomez wrote:
> On 16/07/2025 02.11, Chuck Lever wrote:
>> From: Chuck Lever <chuck.lever@oracle.com>
>>
>> This is useful to avoid generating a whole bunch of unwanted output
>> that can change thread timing.
> 
> What do you mean? Debugging tasks (with debug module) may add delays that can
> affect the playbook time execution?

Yes, or that using "make AV=3" can generate thousands of lines of output
versus just a hundred.


>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> 
> Looks useful. From the docs example looks like import pdb; pdb.set_trace().
> https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_debugger.html#resolving-errors-in-the-debugger
> 
> Can you add the Ansible debugger docs link to the Kconfig?

Yes.


> Reviewed-by: Daniel Gomez <da.gomez@samsung.com>


-- 
Chuck Lever

      reply	other threads:[~2025-07-16 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  0:11 [RFC PATCH 1/2] ansible.cfg: Enable the Ansible debugger when a task fails Chuck Lever
2025-07-16  0:11 ` [RFC PATCH 2/2] ansible.cfg: Explicitly set the ssh user Chuck Lever
2025-07-16 18:05   ` Daniel Gomez
2025-07-16 18:47     ` Chuck Lever
2025-07-16 17:44 ` [RFC PATCH 1/2] ansible.cfg: Enable the Ansible debugger when a task fails Daniel Gomez
2025-07-16 18:38   ` Chuck Lever [this message]

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=289d8634-176c-4788-bb01-8e5ffa5e421d@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@kernel.org \
    --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