From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Report DejaGnu ERROR messages in dg-extract-results
Date: Fri, 23 Sep 2016 11:54:00 -0000 [thread overview]
Message-ID: <ydd37kqc0en.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAKdteOaq=M7NwY3AQ3-0Gn2xE4BFVcZWtnrJJs1Bkk-CH23Mgg@mail.gmail.com> (Christophe Lyon's message of "Tue, 20 Sep 2016 11:26:37 +0200")
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
Hi Christophe,
> We recently faced a problem where a DejaGnu error went un-noticed
> (https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01879.html).
I just noticed that your patch contained an unrelated and bogus change,
reverted as follows. This will only show up on targets that lack (a
sufficiently recent version of) python, Solaris 10 in my case.
Rainer
2016-09-23 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
* dg-extract-results.sh: Revert bogus change.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: dge.patch --]
[-- Type: text/x-patch, Size: 596 bytes --]
diff --git a/contrib/dg-extract-results.sh b/contrib/dg-extract-results.sh
--- a/contrib/dg-extract-results.sh
+++ b/contrib/dg-extract-results.sh
@@ -434,7 +434,7 @@ BEGIN {
/^# of unresolved testcases/ { unrescnt += \$5 }
/^# of unsupported tests/ { unsupcnt += \$5 }
END {
- printf ("\n\t\t=== %s MySummary ===\n\n", tool)
+ printf ("\n\t\t=== %s Summary ===\n\n", tool)
if (dgerrorcnt != 0) printf ("# of DejaGnu errors\t\t%d\n", dgerrorcnt)
if (passcnt != 0) printf ("# of expected passes\t\t%d\n", passcnt)
if (failcnt != 0) printf ("# of unexpected failures\t%d\n", failcnt)
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2016-09-23 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 10:03 Christophe Lyon
2016-09-20 14:57 ` Jeff Law
2016-09-23 11:54 ` Rainer Orth [this message]
2016-09-24 5:46 ` Christophe Lyon
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=ydd37kqc0en.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=christophe.lyon@linaro.org \
--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).