This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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). The patch http://kegel.com/crosstool/current/patches/expect-5.39/pr12096.patch fixes those problems for me.

Also, you might consider using rsh as the transport; see
http://kegel.com/crosstool/current/doc/dejagnu-remote-howto.html and
http://kegel.com/crosstool/current/doc/chroot-login-howto.html
for how I set up things when I was using dejagnu.

Finally, don't forget there's a dejagnu mailing list; see
http://lists.gnu.org/mailman/listinfo/dejagnu
- Dan

--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]