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: Sun, 12 Jul 2009 19:41:00 -0000 [thread overview]
Message-ID: <b609cb3b0907121240r446d6d5eo1d3ddb6a69f9688b@mail.gmail.com> (raw)
In-Reply-To: <b609cb3b0907100914j26cf5a70ia019d4c54418e33e@mail.gmail.com>
On Fri, Jul 10, 2009 at 12:14 PM, NightStrike<nightstrike@gmail.com> wrote:
> 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?
>
More info:
ERROR: tcl error sourcing
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/dg.exp.
ERROR: can't read "status": no such variable
while executing
"list $status [lindex $result 1]"
(procedure "gfortran_load" line 10)
invoked from within
"${tool}_load $output_file"
(procedure "saved-dg-test" line 228)
invoked from within
"saved-dg-test /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/char_bounds_check_fail_1.f90
{ -O0 } { -pedantic-errors}"
("eval" body line 1)
invoked from within
"eval saved-dg-test $args "
(procedure "dg-test" line 9)
invoked from within
"dg-test $test $flags ${default-extra-flags}"
(procedure "gfortran-dg-runtest" line 27)
invoked from within
"gfortran-dg-runtest [lsort \
[glob -nocomplain $srcdir/$subdir/*.\[fF\]{,90,95,03,08} ] ]
$DEFAULT_FFLAGS"
(file "/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/dg.exp"
line 32)
invoked from within
"source /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/dg.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/dg.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp
...
ERROR: tcl error sourcing
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp.
ERROR: torture-init: torture_without_loops is not empty as expected
while executing
"error "torture-init: torture_without_loops is not empty as expected""
invoked from within
"if [info exists torture_without_loops] {
error "torture-init: torture_without_loops is not empty as expected"
}"
(procedure "torture-init" line 4)
invoked from within
"torture-init"
(procedure "gfortran-dg-runtest" line 5)
invoked from within
"gfortran-dg-runtest [lsort \
[find $srcdir/$subdir *.\[fF\]{,90,95,03,08} ] ] " -fopenmp""
(file "/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp"
line 32)
invoked from within
"source /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/graphite/graphite.exp
...
Running /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp
...
ERROR: tcl error sourcing
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp.
ERROR: torture-init: torture_without_loops is not empty as expected
while executing
"error "torture-init: torture_without_loops is not empty as expected""
invoked from within
"if [info exists torture_without_loops] {
error "torture-init: torture_without_loops is not empty as expected"
}"
(procedure "torture-init" line 4)
invoked from within
"torture-init"
(procedure "gfortran-dg-runtest" line 5)
invoked from within
"gfortran-dg-runtest [lsort [glob -nocomplain
$srcdir/$subdir/vect-*.\[fF\]{,90,95,03,08} ]] $DEFAULT_VECTCFLAGS"
(file "/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp"
line 115)
invoked from within
"source /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
ERROR: tcl error sourcing
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp.
ERROR: torture-init: torture_without_loops is not empty as expected
while executing
"error "torture-init: torture_without_loops is not empty as expected""
invoked from within
"if [info exists torture_without_loops] {
error "torture-init: torture_without_loops is not empty as expected"
}"
(procedure "torture-init" line 4)
invoked from within
"torture-init"
(file "/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp"
line 28)
invoked from within
"source /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...
ERROR: tcl error sourcing
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp.
ERROR: torture-init: torture_without_loops is not empty as expected
while executing
"error "torture-init: torture_without_loops is not empty as expected""
invoked from within
"if [info exists torture_without_loops] {
error "torture-init: torture_without_loops is not empty as expected"
}"
(procedure "torture-init" line 4)
invoked from within
"torture-init"
(file "/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp"
line 32)
invoked from within
"source /home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/nightstrike/work/build/gcc-svn/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
next prev parent reply other threads:[~2009-07-12 19:41 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
2009-07-12 19:41 ` NightStrike [this message]
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=b609cb3b0907121240r446d6d5eo1d3ddb6a69f9688b@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).