From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Laurent Vivier" <lvivier@redhat.com>
Subject: float tests are too verbose (was: [PATCH v2] tests/qtest/qom-test: Do not print tested properties by default)
Date: Wed, 18 Jan 2023 14:09:20 +0100 [thread overview]
Message-ID: <e4fb93c6-a28d-b45c-5a7d-48d0ae33b994@redhat.com> (raw)
In-Reply-To: <Y8Z8CJoFyxB9uHqU@redhat.com>
On 17/01/2023 11.44, Daniel P. Berrangé wrote:
...
> And what i think is test float being overly verbose
>
> >> Testing f16_le_quiet
>
> 46464 tests total.
>
> 10000
> 20000
> 30000
> 40000
> 46464 tests performed.
>
> Could be written as
>
> >> Testing f16_le_quiet: 46464 tests total .... OK
>
> (one '.' for each 10,000 tests run, before final 'OK' is printed)
Unfortunately, the float tests are included via a git submodule, so the
source code is not under our direct control here ... has anybody a good idea
how to get this tackled best?
Thomas
next prev parent reply other threads:[~2023-01-18 13:10 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é
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 ` Thomas Huth [this message]
2023-01-18 15:51 ` float tests are too verbose (was: [PATCH v2] tests/qtest/qom-test: Do not print tested properties by default) 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=e4fb93c6-a28d-b45c-5a7d-48d0ae33b994@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).