This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Can't run gfortran testsuite
- From: NightStrike <nightstrike at gmail dot com>
- To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- Cc: fortran at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 10 Jul 2009 12:14:21 -0400
- Subject: Re: Can't run gfortran testsuite
- References: <b609cb3b0907090934l65db3734x5d3719b2f583c266@mail.gmail.com> <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?