From: Pedro Alves <pedro@palves.net>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, gdb-patches@sourceware.org
Subject: Re: [PING] [PATCH] gdb: Remove duplicate "gdb Summary" in the test output
Date: Wed, 6 Jul 2022 20:47:28 +0100 [thread overview]
Message-ID: <b485eeef-01d3-4efd-e3dd-b8cacdcfc54b@palves.net> (raw)
In-Reply-To: <1f72f23c-0355-6684-b3b5-d23a5e37777c@loongson.cn>
On 2022-07-06 1:52 a.m., Tiezhu Yang wrote:
> Hi,
>
> Any comments for this patch?
> Are you OK with this change?
>
> [PATCH] gdb: Remove duplicate "gdb Summary" in the test output
> https://sourceware.org/pipermail/gdb-patches/2022-June/190335.html
>
> It seems that this issue is introduced by commit e83907ff5ffb ("Include count of unexpected core files in gdb.sum summary").
We can't really just remove the printing the tail gdb.sum, as that would
lose the printing of unexpected core files. The commit log of e83907ff5ffb explains:
(...) In the
end, I settled on the script approach for serial mode too, which
requires making the "check-single" rule print the tail end of the
gdb.sum file, with a side effect being that if you look at the
terminal after a run (instead of at the gdb.sum file), you'll see the
"gdb Summary" section twice, once without the unexpected core lines
printed, and then another with. IMO, this isn't an issue; when
testing in parallel mode, if you look at the terminal after "make -jN
check", you'll also see multiple "gdb Summary" sections printed.
If people find this confusing, one idea would be to print some separator, like
below. We'd print it in both serial and parallel modes.
(... snip ...)
=== gdb Summary ===
# of expected passes 115
/home/pedro/rocm/gdb/build/gdb/gdb version 13.0.50.20220706-git -nw -nx -iex "set height 0" -iex "set width 0" -data-directory /home/pedro/rocm/gdb/build/gdb/testsuite/../data-directory
------------------ Final results ------------------
=== gdb Summary ===
# of expected passes 115
/home/pedro/rocm/gdb/build/gdb/gdb version 13.0.50.20220706-git -nw -nx -iex "set height 0" -iex "set width 0" -data-directory /home/pedro/rocm/gdb/build/gdb/testsuite/../data-directory
make[2]: Leaving directory '/home/pedro/rocm/gdb/build/gdb/testsuite'
make[1]: Leaving directory '/home/pedro/rocm/gdb/build/gdb/testsuite'
prev parent reply other threads:[~2022-07-06 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 0:52 Tiezhu Yang
2022-07-06 19:47 ` Pedro Alves [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=b485eeef-01d3-4efd-e3dd-b8cacdcfc54b@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=yangtiezhu@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).