From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/testing/run-tests: add a nose2 debug option
Date: Sat, 10 Aug 2024 00:13:30 +0200 [thread overview]
Message-ID: <20240810001330.576f6cfe@windsurf> (raw)
In-Reply-To: <20240808204812.85880-1-ju.o@free.fr>
On Thu, 8 Aug 2024 22:48:11 +0200
Julien Olivain <ju.o@free.fr> wrote:
> This commit adds the -D/--debug command line options to the
> support/testing/run-tests script.
>
> Using one of those options will pass "--log-level debug" to the
> nose2 invocations. This can be useful to debug nose2 internal
> behaviors. See:
> https://github.com/nose-devs/nose2/blob/0.15.1/nose2/main.py#L209
>
> For example, calling:
>
> support/testing/run-tests --list --debug
>
> will output:
>
> List of tests
> DEBUG:nose2.main:logging initialized debug
> ...
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> For info, this patch was written for a small investigation asked by
> Thomas in the discussion at:
> https://lists.buildroot.org/pipermail/buildroot/2024-August/759983.html
> This debug option might be useful in some other cases...
> ---
> support/testing/run-tests | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-09 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 20:48 [Buildroot] [PATCH 1/1] support/testing/run-tests: add a nose2 debug option Julien Olivain
2024-08-09 22:13 ` Thomas Petazzoni via buildroot [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=20240810001330.576f6cfe@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=ricardo.martincoski@datacom.com.br \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.