From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v2] tests/qtest/qom-test: Do not print tested properties by default
Date: Mon, 16 Jan 2023 14:55:55 +0100 [thread overview]
Message-ID: <e2c4c128-09e1-a97d-83c7-bb580a676de8@linaro.org> (raw)
In-Reply-To: <20221215153036.422362-1-thuth@redhat.com>
On 15/12/22 16:30, Thomas Huth wrote:
> We're still running into the problem that some logs are cut in the
> gitlab-CI since they got too big. The biggest part of the log is
> still the output of the qom-test. Let's stop printing the properties
> by default to get to a saner size here. The full output can still
> be enabled by setting V=2 (or higher) in the environment.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Use atoi() to do proper checking of the verbosity level
>
> tests/qtest/qom-test.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-01-16 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 15:30 [PATCH v2] tests/qtest/qom-test: Do not print tested properties by default Thomas Huth
2023-01-16 13:55 ` Philippe Mathieu-Daudé [this message]
2023-01-16 16:55 ` Peter Maydell
2023-01-17 10:23 ` Peter Maydell
2023-01-17 10:32 ` Thomas Huth
2023-01-17 10:44 ` Daniel P. Berrangé
2023-01-17 11:16 ` Peter Maydell
2023-01-17 12:02 ` Daniel P. Berrangé
2023-01-17 12:22 ` Peter Maydell
2023-01-17 12:26 ` Daniel P. Berrangé
2023-01-18 12:55 ` Thomas Huth
2023-01-18 12:57 ` Daniel P. Berrangé
2023-01-18 13:09 ` float tests are too verbose (was: [PATCH v2] tests/qtest/qom-test: Do not print tested properties by default) Thomas Huth
2023-01-18 15:51 ` Alex Bennée
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=e2c4c128-09e1-a97d-83c7-bb580a676de8@linaro.org \
--to=philmd@linaro.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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).