From: David Blaikie <dblaikie@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: dg-extract-results.sh truncates logs containing "Running "
Date: Tue, 15 Jan 2013 17:16:00 -0000 [thread overview]
Message-ID: <CAENS6EtrYkpqnNVDbqNwRwup_1TGkh3jOi7Gg6LG1f-GCy77hQ@mail.gmail.com> (raw)
In-Reply-To: <CAENS6EtJx3UqHvNiqrpdM-zduMyPYv=X=5UVD3eQ1JLX_evLnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
& now with an actual GCC patch, instead of the GDB one - sorry about that.
On Tue, Jan 15, 2013 at 8:31 AM, David Blaikie <dblaikie@gmail.com> wrote:
> The regex to detect the beginning of a test file execution was too
> broad, matching any line beginning with "Running ". This caused
> dg-extract-results.sh to truncate some test logs, including
> gdb.base/help.exp in the GDB test suite (which tests "help running",
> printing "Running the program.")
>
> The attached patch makes the match a little more precise to avoid
> this. With this the exact count of PASS/FAIL/etc lines in the
> dg-extract-results.sh output matches the counts in the computed
> summary exactly for all cases I've seen.
>
> I encountered this in the GDB test suite but was asked to submit the
> change upstream to GCC as GDB would prefer to avoid unnecessary local
> changes to the script & this change seems general enough to go in to
> GCC.
>
> I'm still a little fuzzy on the specifics of ChangeLog lines, but
> here's my attempt at one for this change:
>
> * dg-extract-results.sh: constrain the start-of-log pattern to
> avoid accidentally matching test content
[-- Attachment #2: gcc-extract-running.diff --]
[-- Type: application/octet-stream, Size: 428 bytes --]
Index: contrib/dg-extract-results.sh
===================================================================
--- contrib/dg-extract-results.sh (revision 195208)
+++ contrib/dg-extract-results.sh (working copy)
@@ -288,7 +288,7 @@
/^Using / {
if (variant == curvar && print_using) { print; next }
}
-/^Running / {
+/^Running .*\\.exp \\.\\.\\./ {
print_using=0
if (variant == curvar) {
if (need_close) close(curfile)
next prev parent reply other threads:[~2013-01-15 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:31 David Blaikie
2013-01-15 17:16 ` David Blaikie [this message]
2013-01-15 20:21 ` Janis Johnson
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=CAENS6EtrYkpqnNVDbqNwRwup_1TGkh3jOi7Gg6LG1f-GCy77hQ@mail.gmail.com \
--to=dblaikie@gmail.com \
--cc=gcc-patches@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).