Posted at, creating PR as its tracker:
http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00309.html
while *.sum files were OK the *.log files sometimes miss the content present
in *.sum results. For example [GDB 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 "/===/".
contrib/
2010-03-08 Jan Kratochvil <jan.kratoch...@redhat.com>
Fix *.log tests output containing "===".
* dg-extract-results.sh (/\===/): Rename to ...
(/^\t\t=== .* ===$/): ... this pattern.
--
Summary: Fix *.log tests merged output containing "==="
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jan dot kratochvil at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43482
