From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH] tests/qtest: Decrease the amount of output from the qom-test
Date: Mon, 21 Nov 2022 16:07:03 -0500 [thread overview]
Message-ID: <CAJSP0QXC9+N5NsGEJeqxhGLpOFBTRDcWmeh3-pJMHNTaPaENZA@mail.gmail.com> (raw)
In-Reply-To: <20221121194240.149268-1-thuth@redhat.com>
On Mon, 21 Nov 2022 at 14:44, Thomas Huth <thuth@redhat.com> wrote:
>
> The logs in the gitlab-CI have a size constraint, and sometimes
> we already hit this limit. The biggest part of the log then seems
> to be filled by the qom-test, so we should decrease the size of
> the output - which can be done easily by not printing the path
> for each property, since the path has already been logged at the
> beginning of each node that we handle here.
>
> However, if we omit the path, we should make sure to not recurse
> into child nodes in between, so that it is clear to which node
> each property belongs. Thus store the children and links in a
> temporary list and recurse only at the end of each node, when
> all properties have already been printed.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> See e.g. here for a log that got too big:
> https://gitlab.com/qemu-project/qemu/-/jobs/3355901224
>
> tests/qtest/qom-test.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
Nice!
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
prev parent reply other threads:[~2022-11-21 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 19:42 [PATCH] tests/qtest: Decrease the amount of output from the qom-test Thomas Huth
2022-11-21 21:07 ` Stefan Hajnoczi [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=CAJSP0QXC9+N5NsGEJeqxhGLpOFBTRDcWmeh3-pJMHNTaPaENZA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).