public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-4333] Harmonize headers between both dg-extract-results scripts
Date: Fri, 29 Sep 2023 14:51:31 +0000 (GMT)	[thread overview]
Message-ID: <20230929145131.4576B3858C50@sourceware.org> (raw)

https://gcc.gnu.org/g:346f5991569faeb9995ac12100c2afba46ab6437

commit r14-4333-g346f5991569faeb9995ac12100c2afba46ab6437
Author: Paul Iannetta <piannetta@kalrayinc.com>
Date:   Fri Sep 29 08:50:28 2023 -0600

    Harmonize headers between both dg-extract-results scripts
    
        The header of the python version looked like:
        Target is ...
        Host   is ...
        The header of the bash version looked like:
        Test run by ... on ...
        Target is ...
    
        After this change both headers look like:
        Test run by ... on ...
        Target is ...
        Host   is ...
    
        The order of the tests is not the same but since dg-cmp-results.sh it
        does not matter much.
    
    contrib/ChangeLog:
    
            * dg-extract-results.py: Print the "Test run" line.
            * dg-extract-results.sh: Print the "Host" line.

Diff:
---
 contrib/dg-extract-results.py | 2 +-
 contrib/dg-extract-results.sh | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/contrib/dg-extract-results.py b/contrib/dg-extract-results.py
index 7c2eb48fcd0..0bc65d30eaf 100644
--- a/contrib/dg-extract-results.py
+++ b/contrib/dg-extract-results.py
@@ -113,7 +113,7 @@ class Prog:
         # Whether to create .sum rather than .log output.
         self.do_sum = True
         # Regexps used while parsing.
-        self.test_run_re = re.compile (r'^Test Run By (\S+) on (.*)$')
+        self.test_run_re = re.compile (r'^Test run by (\S+) on (.*)$')
         self.tool_re = re.compile (r'^\t\t=== (.*) tests ===$')
         self.result_re = re.compile (r'^(PASS|XPASS|FAIL|XFAIL|UNRESOLVED'
                                      r'|WARNING|ERROR|UNSUPPORTED|UNTESTED'
diff --git a/contrib/dg-extract-results.sh b/contrib/dg-extract-results.sh
index 33968ed7b23..2a25d2c81db 100755
--- a/contrib/dg-extract-results.sh
+++ b/contrib/dg-extract-results.sh
@@ -271,7 +271,7 @@ cat $SUM_FILES \
 
 # Write the begining of the combined summary file.
 
-head -n 2 $FIRST_SUM
+head -n 3 $FIRST_SUM
 echo
 echo "		=== $TOOL tests ==="
 echo

                 reply	other threads:[~2023-09-29 14:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230929145131.4576B3858C50@sourceware.org \
    --to=law@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).