From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] tests/qtest/qom-test: Do not print tested properties by default
Date: Thu, 15 Dec 2022 15:12:06 +0100 [thread overview]
Message-ID: <2c88fd8e-a1f7-2cf1-ec90-46c71421af73@redhat.com> (raw)
In-Reply-To: <CAFEAcA9JKHV+TNCFjgHsLkoMQ1eVz6d_hbre6OqZVasawdn=2A@mail.gmail.com>
On 15/12/2022 15.04, Peter Maydell wrote:
> On Thu, 15 Dec 2022 at 14:01, Thomas Huth <thuth@redhat.com> 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>
>
>> @@ -103,6 +107,12 @@ static void add_machine_test_case(const char *mname)
>>
>> int main(int argc, char **argv)
>> {
>> + char *v_env = getenv("V");
>> +
>> + if (v_env && *v_env >= '2') {
>> + verbose = true;
>> + }
>
> This is a bit cheesy -- I think we should parse the string
> to a number properly rather than accepting '2', '23',
> '2.89237', '2e45' '2fast2furious' etc :-)
Ok, true, it's a little bit weird that it's verbose for V=9 but not for V=10
... I'll rework the patch and send a patch for hmp-test.c, too (where I've
copied the code from).
Thomas
prev parent reply other threads:[~2022-12-15 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:01 [PATCH] tests/qtest/qom-test: Do not print tested properties by default Thomas Huth
2022-12-15 14:04 ` Peter Maydell
2022-12-15 14:12 ` Thomas Huth [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=2c88fd8e-a1f7-2cf1-ec90-46c71421af73@redhat.com \
--to=thuth@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).