From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: dwarves@vger.kernel.org, Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH dwarves 2/2] tests/btf_functions: reduce verbosity of test
Date: Thu, 3 Oct 2024 11:56:53 -0300 [thread overview]
Message-ID: <Zv6wtQHQvmt5PbOy@x1> (raw)
In-Reply-To: <20241002113326.792495-3-alan.maguire@oracle.com>
On Wed, Oct 02, 2024 at 12:33:26PM +0100, Alan Maguire wrote:
> when in non-verbose mode, emit a single line describing test + result.
>
> Non-verbose output now looks like this:
>
> 1: Validation of BTF encoding of functions; this may take some time: Ok
Thanks, looks great now!
I added this to the commit log message so that we see how a full
tests/tests runs looks like:
Committer testing:
acme@x1:~/git/pahole$ time tests/tests
1: Validation of BTF encoding of functions; this may take some time: Ok
2: Pretty printing of files using DWARF type information: Ok
3: Parallel reproducible DWARF Loading/Serial BTF encoding: Ok
/home/acme/git/pahole
real 10m54.784s
user 9m43.335s
sys 5m14.034s
acme@x1:~/git/pahole$ grep -m1 "model name" /proc/cpuinfo
model name : 13th Gen Intel(R) Core(TM) i7-1365U
acme@x1:~/git/pahole$
Suggested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
next prev parent reply other threads:[~2024-10-03 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 11:33 [PATCH dwarves 0/2] tests: reproducible_build/btf_functions fix Alan Maguire
2024-10-02 11:33 ` [PATCH dwarves 1/2] tests/reproducible_build: fix vmlinux finding logic Alan Maguire
2024-10-02 11:33 ` [PATCH dwarves 2/2] tests/btf_functions: reduce verbosity of test Alan Maguire
2024-10-03 14:56 ` Arnaldo Carvalho de Melo [this message]
2024-10-03 14:39 ` [PATCH dwarves 0/2] tests: reproducible_build/btf_functions fix Arnaldo Carvalho de Melo
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=Zv6wtQHQvmt5PbOy@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alan.maguire@oracle.com \
--cc=dwarves@vger.kernel.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