From: Andrew Burgess <aburgess@redhat.com>
Date: Mon, 23 Jun 2025 15:32:28 +0000 (+0100)
Subject: gdb: create gdb.sum/gdb.log summary after using check-all-boards
X-Git-Tag: binutils-2_45~178
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1fe6ffd81e76a2799add18d9e1d5208a90c21ece;p=thirdparty%2Fbinutils-gdb.git

gdb: create gdb.sum/gdb.log summary after using check-all-boards

Use the contrib/dg-extract-results.sh script to create a gdb.sum and
gdb.log summary after running the check-all-boards make target.

Having the results from all the boards merged into a single file
isn't (maybe) the most useful, but it isn't a bad thing.  However, the
great thing about merge the results is that the totals are also
merged.

The 'check-all-boards' recipe can then extract these totals, just as
we do for the normal 'check' recipe, this makes is much easier to
spot if there are any unexpected failures when using
'check-all-boards'.

Reviewed-By: Keith Seitz <keiths@redhat.com>
---

diff --git a/gdb/testsuite/Makefile.in b/gdb/testsuite/Makefile.in
index 4a6665d4483..fa2d9eb8c0e 100644
--- a/gdb/testsuite/Makefile.in
+++ b/gdb/testsuite/Makefile.in
@@ -386,7 +386,17 @@ check-all-boards: all $(abs_builddir)/site.exp
 	${abs_srcdir}/make-check-all.sh --keep-results \
 		--host-user "$(GDB_HOST_USERNAME)" \
 		--target-user "$(GDB_TARGET_USERNAME)" \
-		"$(TESTS)"
+		"$(TESTS)" \
+	result=$$?; \
+	if test -d check-all; then \
+	  $(SHELL) $(srcdir)/../../contrib/dg-extract-results.sh \
+	    `find check-all -name gdb.sum -print` > check-all/gdb.sum; \
+	  $(SHELL) $(srcdir)/../../contrib/dg-extract-results.sh -L \
+	    `find check-all -name gdb.log -print` > check-all/gdb.log; \
+	  sed -n '/=== gdb Summary ===/,$$ p' check-all/gdb.sum; \
+	fi; \
+	exit $$result
+
 
 force:;