public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarthjw at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/64983] Incomplete summary when regtesting with dejagnu 1.5.2.
Date: Sun, 29 Mar 2015 07:17:00 -0000 [thread overview]
Message-ID: <bug-64983-4-dFvXnG4DuM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64983-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
Jack Howarth <howarthjw at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarthjw at gmail dot com
--- Comment #8 from Jack Howarth <howarthjw at gmail dot com> ---
The usage of reset_vars in proc runtest results in the execution of...
foreach x $test_names {
set test_counts($x,count) 0
}
Reverting the commit while effectively retaining that part of the changes
with...
diff -uNr dejagnu-1.5.2.orig/runtest.exp dejagnu-1.5.2/runtest.exp
--- dejagnu-1.5.2.orig/runtest.exp 2015-02-03 21:25:26.000000000 -0500
+++ dejagnu-1.5.2/runtest.exp 2015-03-28 16:48:10.000000000 -0400
@@ -1441,13 +1441,22 @@
#
proc runtest { test_file_name } {
+ global test_names test_counts
+ global prms_id
+ global bug_id
global test_result
global errcnt
global errorInfo
global tool
clone_output "Running $test_file_name ..."
- reset_vars
+ set prms_id 0
+ set bug_id 0
+
+ foreach x $test_names {
+ set test_counts($x,count) 0
+ }
+
set test_result ""
if {[file exists $test_file_name]} {
...replicates the breakage.
next prev parent reply other threads:[~2015-03-28 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 14:24 [Bug testsuite/64983] New: " dominiq at lps dot ens.fr
2015-02-09 14:36 ` [Bug testsuite/64983] " dominiq at lps dot ens.fr
2015-02-18 17:55 ` howarth at bromo dot med.uc.edu
2015-02-18 19:37 ` iains at gcc dot gnu.org
2015-02-18 20:15 ` howarth at bromo dot med.uc.edu
2015-02-18 20:21 ` iains at gcc dot gnu.org
2015-03-28 18:07 ` howarth at bromo dot med.uc.edu
2015-03-28 20:56 ` howarth at bromo dot med.uc.edu
2015-03-29 7:17 ` howarthjw at gmail dot com [this message]
2015-03-29 15:10 ` howarth.at.gcc at gmail dot com
2015-03-29 15:39 ` dominiq at lps dot ens.fr
2015-03-31 5:09 ` howarth.at.gcc at gmail dot com
2015-03-31 9:34 ` dominiq at lps dot ens.fr
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=bug-64983-4-dFvXnG4DuM@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).