public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb: Remove duplicate "gdb Summary" in the test output
Date: Sat, 25 Jun 2022 11:31:05 +0800	[thread overview]
Message-ID: <1656127865-10255-1-git-send-email-yangtiezhu@loongson.cn> (raw)

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"

we can see the following info in the output:

  Running /home/loongson/gdb.git/gdb/testsuite/gdb.base/a2-run.exp ...

          === gdb Summary ===

  # of expected passes        9
  /home/loongson/build.git/gdb/gdb version  13.0.50.20220625-git ...

          === gdb Summary ===

  # of expected passes        9
  /home/loongson/build.git/gdb/gdb version  13.0.50.20220625-git ...

Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
 gdb/testsuite/Makefile.in | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gdb/testsuite/Makefile.in b/gdb/testsuite/Makefile.in
index 87ba522..aa0c00f 100644
--- a/gdb/testsuite/Makefile.in
+++ b/gdb/testsuite/Makefile.in
@@ -212,7 +212,6 @@ check-single:
 	$(DO_RUNTEST) $(RUNTESTFLAGS) $(expanded_tests_or_none) $(TIMESTAMP); \
 	result=$$?; \
 	$(SHELL) $(srcdir)/lib/dg-add-core-file-count.sh; \
-	sed -n '/=== gdb Summary ===/,$$ p' gdb.sum; \
 	exit $$result
 
 check-single-racy:
-- 
2.1.0


             reply	other threads:[~2022-06-25  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25  3:31 Tiezhu Yang [this message]
2022-07-15 16:34 ` Tom Tromey

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=1656127865-10255-1-git-send-email-yangtiezhu@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).