From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: [patch] Fix *.log tests merged output containing "==="
Date: Mon, 08 Mar 2010 23:10:00 -0000 [thread overview]
Message-ID: <20100308231019.GA19312@host0.dyn.jankratochvil.net> (raw)
Hi,
while *.sum files were OK the *.log files sometimes miss the content present
in *.sum results. For example gdb.base/bitfields.exp output was missing while
gdb.base/bitfields.exp output was present.
It got broken if arbitrary "===" string has appeared in the tests output.
Grepped dejagnu the proposed more strict pattern should match fine:
$ grep === `rpm -ql dejagnu`
/usr/share/dejagnu/framework.exp: clone_output "\n\t\t=== $tool Summary for $current_target_name ===\n"
/usr/share/dejagnu/framework.exp: clone_output "\n\t\t=== $tool Summary ===\n"
/usr/share/dejagnu/runtest.exp:clone_output "\n\t\t=== $tool tests ===\n"
For GDB `grep '^Running ' gdb.log | wc -l' changes 1770 -> 1818.
For GCC `cat *.log | wc -l' changes 444633 -> 482178.
(checked the output change looks OK for both cases)
I am not aware why there was "/\===/" instead of just "/===/".
OK to check-in? (GCC + GDB approval requested)
Thanks,
Jan
gdb/testsuite/ | contrib/
2010-03-08 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix *.log tests output containing "===".
* dg-extract-results.sh (/\===/): Rename to ...
(/^\t\t=== .* ===$/): ... this pattern.
--- a/gdb/testsuite/dg-extract-results.sh
+++ b/gdb/testsuite/dg-extract-results.sh
@@ -299,7 +299,7 @@ BEGIN {
next
}
}
-/\===/ { curvar = ""; next }
+/^\t\t=== .* ===$/ { curvar = ""; next }
/^(PASS|XPASS|FAIL|XFAIL|UNRESOLVED|WARNING|ERROR|UNSUPPORTED|UNTESTED|KFAIL):/ {
testname=\$2
# Ugly hack for gfortran.dg/dg.exp
next reply other threads:[~2010-03-08 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:10 Jan Kratochvil [this message]
2010-03-22 19:40 ` Tom Tromey
2010-03-22 20:24 ` Jan Kratochvil
2010-03-22 20:26 ` Tom Tromey
2010-03-22 20:41 ` Jan Kratochvil
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=20100308231019.GA19312@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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