From: Simon Glass <sjg@chromium.org>
To: Simon Glass <sjg@chromium.org>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Philippe Reynes <philippe.reynes@softathome.com>,
Marek Vasut <marex@denx.de>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v2 03/11] patman: Don't buffer test output with a single test
Date: Sun, 21 Aug 2022 00:10:34 +0000 [thread overview]
Message-ID: <CAPnjgZ11pAALYbMVZeMyrmCN+H_xPjyY2_juPXG90Shbd7XfNw@mail.gmail.com> (raw)
In-Reply-To: <20220813174051.1813081-4-sjg@chromium.org>
When a single test is run we don't need to buffer the test output. This
has the unfortunate side effect of suppressing test output, in particular
the binman output directory normally printed with the -X option. This is
a huge problem since it blocks debugging of tests.
We don't actually know how many tests will be run when we set up the
suite, so as a work-around, assume that test_name being specified
indicates that there is likely only one.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
(no changes since v1)
tools/patman/test_util.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Applied to u-boot-dm, thanks!
next prev parent reply other threads:[~2022-08-21 0:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 17:40 [PATCH v2 00/11] binman: Enhancements to binman mkimage Simon Glass
2022-08-13 17:40 ` [PATCH v2 01/11] doc: Build documentation in parallel Simon Glass
2022-08-20 21:33 ` Simon Glass
2022-08-27 1:59 ` Simon Glass
2022-08-13 17:40 ` [PATCH v2 02/11] patman: Put the coverage command-line last Simon Glass
2022-08-13 17:40 ` [PATCH v2 03/11] patman: Don't buffer test output with a single test Simon Glass
2022-08-13 17:40 ` [PATCH v2 04/11] binman: Fix up the entry-docs for Entry_pre_load Simon Glass
2022-08-13 17:40 ` [PATCH v2 05/11] binman: Add a way to check for missing properties Simon Glass
2022-08-13 17:40 ` [PATCH v2 06/11] binman: Adjust mkimage etype node reading Simon Glass
2022-08-13 17:40 ` [PATCH v2 07/11] binman: Avoid use of expected failure Simon Glass
2022-08-13 17:40 ` [PATCH v2 08/11] binman: Improve mkimage documentation Simon Glass
2022-08-13 17:40 ` [PATCH v2 09/11] binman: Allow the image name to be the data file Simon Glass
2022-08-13 17:40 ` [PATCH v2 10/11] binman: Allow passing entries using -n Simon Glass
2022-08-13 17:40 ` [PATCH v2 11/11] binman: Allow collection to use entries from other sections Simon Glass
2022-08-21 0:10 ` Simon Glass
2022-08-21 0:10 ` [PATCH v2 09/11] binman: Allow the image name to be the data file Simon Glass
2022-08-21 0:10 ` [PATCH v2 10/11] binman: Allow passing entries using -n Simon Glass
2022-08-21 0:10 ` [PATCH v2 08/11] binman: Improve mkimage documentation Simon Glass
2022-08-21 0:10 ` [PATCH v2 07/11] binman: Avoid use of expected failure Simon Glass
2022-08-21 0:10 ` [PATCH v2 06/11] binman: Adjust mkimage etype node reading Simon Glass
2022-08-21 0:10 ` [PATCH v2 05/11] binman: Add a way to check for missing properties Simon Glass
2022-08-21 0:10 ` [PATCH v2 04/11] binman: Fix up the entry-docs for Entry_pre_load Simon Glass
2022-08-21 0:10 ` Simon Glass [this message]
2022-08-21 0:10 ` [PATCH v2 02/11] patman: Put the coverage command-line last Simon Glass
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=CAPnjgZ11pAALYbMVZeMyrmCN+H_xPjyY2_juPXG90Shbd7XfNw@mail.gmail.com \
--to=sjg@chromium.org \
--cc=alpernebiyasak@gmail.com \
--cc=marex@denx.de \
--cc=philippe.reynes@softathome.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).