public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <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: Sat, 28 Mar 2015 20:56:00 -0000 [thread overview]
Message-ID: <bug-64983-4-8P088XNUot@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
--- Comment #7 from howarth at bromo dot med.uc.edu ---
A regression hunt of dejagnu master revealed that the offending commit causing
this bug was...
http://git.savannah.gnu.org/cgit/dejagnu.git/commit/?id=6d2e2d3791bcea70131a6cf64a0a5223333a7b8e
2011-03-14 Jan Kratochvil <jan.kratochvil@redhat.com>
* runtest.exp (runtest): Call reset_vars at initialisation so that
a perror does not affect test results in other test scripts.
and that reverting this change in 1.5.2 restores the expected summary output.
This issue is actually predates 1.5.1 but isn't present there because the
original 1.5 branch tree was reused for the 1.5.1 release development whereas
the 1.5.2 release was branched directly off of master.
next prev parent reply other threads:[~2015-03-28 19:25 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 [this message]
2015-03-29 7:17 ` howarthjw at gmail dot com
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-8P088XNUot@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).