From: Tom Tromey <tom@tromey.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Remove duplicate "gdb Summary" in the test output
Date: Fri, 15 Jul 2022 10:34:03 -0600 [thread overview]
Message-ID: <87v8rypc78.fsf@tromey.com> (raw)
In-Reply-To: <1656127865-10255-1-git-send-email-yangtiezhu@loongson.cn> (Tiezhu Yang's message of "Sat, 25 Jun 2022 11:31:05 +0800")
>>>>> Tiezhu Yang <yangtiezhu@loongson.cn> writes:
> There exists duplicate "gdb Summary" in the test output, just modify
> gdb/testsuite/Makefile.in to remove the redundant info.
> Here is an example, when execute the following command:
> make check-gdb TESTS="gdb.base/a2-run.exp"
I think what's happening here is that the "Summary" line is added for
the benefit of parallel "make check". However, in your case, you're
only running a single test. But, if you run many tests, I think the
output won't look redundant. So, I tend to think it should just remain
the way it is.
Tom
prev parent reply other threads:[~2022-07-15 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 3:31 Tiezhu Yang
2022-07-15 16:34 ` Tom Tromey [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=87v8rypc78.fsf@tromey.com \
--to=tom@tromey.com \
--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).