Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] print summary from "make check"
Date: Thu, 14 Nov 2013 21:40:00 -0000	[thread overview]
Message-ID: <87txfevfe4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1383765976-7748-1-git-send-email-tromey@redhat.com> (Tom	Tromey's message of "Wed, 6 Nov 2013 12:26:16 -0700")

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

Tom> Pedro pointed out that it is handy for "make check" to print a summary
Tom> of the results.  This happens in the check-single case and also if you
Tom> invoke runtest by hand.

I'm checking in the appended, which is the fixed up version of this
patch.

Tom

~~~
From 496038b324b44f110d4ef07829c983f748ee9003 Mon Sep 17 00:00:00 2001
From: Tom Tromey <tromey@redhat.com>
Date: Wed, 6 Nov 2013 12:24:21 -0700
Subject: [PATCH] print summary from "make check"

Pedro pointed out that it is handy for "make check" to print a summary
of the results.  This happens in the check-single case and also if you
invoke runtest by hand.

This patch implements the same thing for check-parallel.

2013-11-14  Tom Tromey  <tromey@redhat.com>

	* Makefile.in (check-parallel): Print summary from gdb.sum.
---
 gdb/testsuite/ChangeLog   | 4 ++++
 gdb/testsuite/Makefile.in | 1 +
 2 files changed, 5 insertions(+)

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index ed44b37..121fedb 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2013-11-14  Tom Tromey  <tromey@redhat.com>
+
+	* Makefile.in (check-parallel): Print summary from gdb.sum.
+
 2013-11-14  Omair Javaid  <Omair.Javaid@linaro.org>
 
         * gdb.dwarf2/dw2-case-insensitive-debug.S: Updated compile unit
diff --git a/gdb/testsuite/Makefile.in b/gdb/testsuite/Makefile.in
index 93e9b5b..cdf9550 100644
--- a/gdb/testsuite/Makefile.in
+++ b/gdb/testsuite/Makefile.in
@@ -170,6 +170,7 @@ check-parallel:
 	  `find outputs -name gdb.sum -print` > gdb.sum; \
 	$(SHELL) $(srcdir)/dg-extract-results.sh -L \
 	  `find outputs -name gdb.log -print` > gdb.log
+	@sed -n '/=== gdb Summary ===/,$$ p' gdb.sum
 
 # Turn a list of .exp files into "check/" targets.  Only examine .exp
 # files appearing in a gdb.* directory -- we don't want to pick up
-- 
1.8.1.4


      parent reply	other threads:[~2013-11-14 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 19:36 Tom Tromey
2013-11-06 20:47 ` Tom Tromey
2013-11-14 21:40 ` 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=87txfevfe4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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