From: Bernd Schmidt <bernds_cb1@t-online.de>
To: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: RFA: speeding up dg-extract-results.sh
Date: Sat, 24 May 2014 11:17:00 -0000 [thread overview]
Message-ID: <53807FD2.6060805@t-online.de> (raw)
In-Reply-To: <878utfe5g0.fsf@talisman.default>
On 02/13/2014 10:18 AM, Richard Sandiford wrote:
> contrib/
> * dg-extract-results.py: New file.
> * dg-extract-results.sh: Use it if the environment seems suitable.
I'm now seeing the following:
Traceback (most recent call last):
File "../../git/gcc/../contrib/dg-extract-results.py", line 581, in
<module>
Prog().main()
File "../../git/gcc/../contrib/dg-extract-results.py", line 569, in main
self.output_tool (self.runs[name])
File "../../git/gcc/../contrib/dg-extract-results.py", line 534, in
output_tool
self.output_variation (tool, variation)
File "../../git/gcc/../contrib/dg-extract-results.py", line 483, in
output_variation
for harness in sorted (variation.harnesses.values()):
TypeError: unorderable types: HarnessRun() < HarnessRun()
$ /usr/bin/python --version
Python 3.3.3
Bernd
next prev parent reply other threads:[~2014-05-24 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:18 Richard Sandiford
2014-05-03 7:34 ` Ping: " Richard Sandiford
2014-05-05 19:17 ` Jakub Jelinek
2014-05-05 20:36 ` Richard Sandiford
2014-05-03 20:07 ` Mike Stump
2014-05-05 16:08 ` Jeff Law
2014-05-05 18:15 ` Mike Stump
2014-05-05 18:16 ` Jeff Law
[not found] ` <CADnVucCA0ozSz=x3z8vexBOkWRj3pquKVuWsFq4xZre0CfxFyQ@mail.gmail.com>
2014-05-19 18:07 ` Richard Sandiford
2014-05-19 18:49 ` Charles Baylis
2014-05-20 10:09 ` Richard Sandiford
2014-05-24 11:17 ` Bernd Schmidt [this message]
2014-05-24 17:15 ` Mike Stump
2014-05-24 17:53 ` Trevor Saunders
2014-05-25 9:35 ` Richard Sandiford
2014-06-12 15:53 ` Bernd Schmidt
2014-06-12 16:32 ` Mike Stump
2014-06-14 9:50 ` Richard Sandiford
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=53807FD2.6060805@t-online.de \
--to=bernds_cb1@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.com \
/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).