From: NightStrike <nightstrike@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: fortran@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Can't run gfortran testsuite
Date: Fri, 10 Jul 2009 16:14:00 -0000 [thread overview]
Message-ID: <b609cb3b0907100914j26cf5a70ia019d4c54418e33e@mail.gmail.com> (raw)
In-Reply-To: <20090709185208.GA58596@troutmask.apl.washington.edu>
On Thu, Jul 9, 2009 at 2:52 PM, Steve
Kargl<sgk@troutmask.apl.washington.edu> wrote:
> On Thu, Jul 09, 2009 at 12:34:00PM -0400, NightStrike wrote:
>> I have been trying to run the gfortran testsuite for a while now, and
>> it keeps falling apart. Dominiq tried to find a revision that might
>> attribute to it, and though r147421 might have something to do with
>> it: http://gcc.gnu.org/viewcvs?view=rev&revision=147421
>>
>> These are the errors I get that prevent the testsuite from running
>> more than a few thousand tests:
>>
>> ERROR: tcl error sourcing
>> /dev/shm/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/dg.exp.
>> ERROR: can't read "status": no such variable
>> ERROR: tcl error sourcing
>> /dev/shm/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp.
>> ERROR: torture-init: torture_without_loops is not empty as expected
>> ERROR: tcl error sourcing
>> /dev/shm/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp.
>> ERROR: torture-init: torture_without_loops is not empty as expected
>> ERROR: tcl error sourcing
>> /dev/shm/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp.
>> ERROR: torture-init: torture_without_loops is not empty as expected
>> ERROR: tcl error sourcing
>> /dev/shm/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp.
>> ERROR: torture-init: torture_without_loops is not empty as expected
>
> This appears to be a general testsuite issue. You try pinging Janis
> on IRC. She may have an idea on the cause.
I'm also emailing the general gcc list about this. Does anyone have
any idea on how to handle this situation?
next parent reply other threads:[~2009-07-10 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b609cb3b0907090934l65db3734x5d3719b2f583c266@mail.gmail.com>
[not found] ` <20090709185208.GA58596@troutmask.apl.washington.edu>
2009-07-10 16:14 ` NightStrike [this message]
2009-07-12 19:41 ` NightStrike
2009-07-13 18:34 ` Janis Johnson
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=b609cb3b0907100914j26cf5a70ia019d4c54418e33e@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).