Re: RFH: dejagnu and make check using remote testing host...

[David Daney <ddaney@avtrex.com>]

Dan Kegel wrote:
> ddaney@avtrex.com wrote:
> 
>>I have configured dejagnu for testing a GCC cross compiler on a network
>>connected board.  The configuration worked well for me on GCC-3.3.x and
>>3.4.x, however something wierd is happening to me for the current mainline.
>>
>>Some of the execution tests run correctly, in others it looks like the
>>testsuite dirvers/dejagnu thinks the ftp of the executable to the target
>>fails when it is still in progress, or in other cases it tries to
>>execute the programs before they have been transfered.
>>
>>running make check from libffi or libjava works fine.  The problems I am
>>seeing are in gcc.c-torture/execute
>>
>>The configuration is as follows:
>>
>>--host=i686-pc-linux-gnu --target=mipsel-linux
>>
>>Attached is a fragment of gcc.log.
>>
>>Can anyone think of what the problem might be?
>>
>>Executing on host: /newdisk/programs/mipsel-gccmaincvs/gcc/xgcc -B/newdisk/programs/mipsel-gccmaincvs/gcc/ /newdisk/programs/gccmaincvs/gcc/gcc/testsuite/gcc.c-torture/execute/20000113-1.c  -w  -O0   -lm   -o /newdisk/programs/mipsel-gccmaincvs/gcc/testsuite/20000113-1.x0    (timeout = 300)
>>PASS: gcc.c-torture/execute/20000113-1.c compilation,  -O0 
>>...
>>ftp> put /newdisk/programs/mipsel-gccmaincvs/gcc/testsuite/20000113-1.x0 /tmp/20000113-1.x0.15879
>>Download of /newdisk/programs/mipsel-gccmaincvs/gcc/testsuite/20000113-1.x0 to proton3 failed.
>>UNRESOLVED: gcc.c-torture/execute/20000113-1.c execution,  -O0 
> 
> 
> Which version of expect are you using?  The stock one
> has a bug which causes occasional spurious failures,
> described in http://gcc.gnu.org/PR12096
> (I haven't seen the one you're seeing, but then, I've never
>   used FTP as a transport when using dejagnu).

I upgraded to the latest TCL, expect and dejagnu and still had the problems.

> 
> Also, you might consider using rsh as the transport; see

I think the ftp transport is screwed up.  I switched to rcp with this
board file:

-------------8<---------------------
load_base_board_description "unix";

# The generic type of board.
set board_info($board,generic_name) "unix"

# The name used to connect to this machine.
set board_info($board,hostname) "proton3"

set board_info($board,ftp_directory) "/tmp"

set prefix_dir "/tmp"
--------------8<--------------------

Kind of a mixture of what I got from Andrew Haley and your site.


and it is magically working again.  The ftp method used to work for me,
but something changed somewhere.....


Thanks for your help,

David Daney.