* Mauve halts after first error. @ 2004-07-04 23:57 ` James Damour 2004-07-05 3:43 ` Stephen Crawley 0 siblings, 1 reply; 3+ messages in thread From: James Damour @ 2004-07-04 23:57 UTC (permalink / raw) To: mauve-discuss [-- Attachment #1: Type: text/plain, Size: 1763 bytes --] I am attempting to run the Mauve test suite that was downloaded as part of fitzsim's jhbuild of gcj. Sadly, when the test suite exits after it finds the first error. Any help in configuring or otherwise running the testsuite so it exercises all tests would be greatly appreciated. The proceedure I follow is as follows: 1) jhbuild build 2) cd .../mauve 3) ln -s <gcc source tree>/libjava/mauve-libgcj mauve-libgcj 4) ./configure --with-gcj 5) make KEYS=libgcj check The last few lines are: CLASSPATH=.:. gcj -fassume-compiled -g -O2 -c -o gnu/testlet/java/beans/DescriptorTest.o gnu/testlet/java/beans/DescriptorTest.java CLASSPATH=.:. gcj -fassume-compiled -g -O2 -c -o gnu/testlet/java/beans/Expression/check.o gnu/testlet/java/beans/Expression/check.java gnu/testlet/java/beans/Expression/check.java:30: error: Class or interface `java.beans.Expression' not found in import. import java.beans.Expression; ^ gnu/testlet/java/beans/Expression/check.java:76: error: Type `Expression' not found in the declaration of the local variable `expr'. Expression expr = new Expression(d, "method", arg1); ^ 2 errors make[1]: *** [gnu/testlet/java/beans/Expression/check.o] Error 1 make[1]: Leaving directory `/home/james/projects/gcc/sources/jhbuild-src/gcc/libjava/testsuite/libjava.mauve/mauve' make: *** [check-am] Error 2 I have the following autotools installed (on an up-to-date Debian Sarge system): autoconf: 2.59-5 automake1.4: 1:1.4-p6-8 automake1.6: 1.6.3-11 automake1.7: 1.7.9-6 automake1.8: 1.8.5-1 autoproject: 0.17-1 autotools-dev: 20040312.1 Please let me know if there is any additional information I can send. -- James Damour (Suvarov454) <suvarov454@users.sourceforge.net> [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Mauve halts after first error. 2004-07-04 23:57 ` Mauve halts after first error James Damour @ 2004-07-05 3:43 ` Stephen Crawley 2004-07-05 6:18 ` Mark Wielaard 0 siblings, 1 reply; 3+ messages in thread From: Stephen Crawley @ 2004-07-05 3:43 UTC (permalink / raw) To: James Damour (Suvarov454); +Cc: mauve-discuss, crawley Hi, I ran into this particular problem too. Someone has checked in a Mauve test case that refers to a class that Classpath does not yet support. [I wish people wouldn't do this!] The workaround is to add the following line to your keys file: !java.beans.Expression.check -- Steve ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Mauve halts after first error. 2004-07-05 3:43 ` Stephen Crawley @ 2004-07-05 6:18 ` Mark Wielaard 0 siblings, 0 replies; 3+ messages in thread From: Mark Wielaard @ 2004-07-05 6:18 UTC (permalink / raw) To: Stephen Crawley; +Cc: James Damour (Suvarov454), mauve-discuss, crawley [-- Attachment #1: Type: text/plain, Size: 1856 bytes --] Hi, On Mon, 2004-07-05 at 05:42, Stephen Crawley wrote: > I ran into this particular problem too. Someone has checked in a Mauve > test case that refers to a class that Classpath does not yet support. > [I wish people wouldn't do this!] > > The workaround is to add the following line to your keys file: > > !java.beans.Expression.check Note that in this particular case GNU Classpath now includes this class (since yesterday, just in time for 0.10-pre1!). Since I also ran into this problem so often (or having a runtime crash or hang on a particular test) I created the batch_run and runner scripts which are now included in mauve CVS, but you need to edit them by hand at the moment for your compiler/runtime setup. See the README: An alternative way to compiling and running all tests is the batch_run script. This makes it easy to run all test in one batch without worrying wheter all tests compile and/or running them crashes or hangs the runtime. batch_run and the runner helper script aren't integrated with the configure setup yet so you will have to edit them by hand to explicitly set the COMPILER variable in batch_run and the RUNTIME variable in runner. Optionally you can also change the KEYS setting in batch_run if you don't want to run all tests. You can also set the variable NATIVE=true in batch_run when you want to use gcj (without -C) in native mode. When a test cannot be compiled with the given COMPILER batch_run will output FAIL: <testname> COMPILE FAILED and go on with the next test. If the runner detects a runtime crash or timeout (runner variable WAIT=60 seconds) it will output FAIL: <testname> CRASH or TIMEOUT. Cheers, Mark [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-07-05 6:18 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <jdamour@nycap.rr.com> 2004-07-04 23:57 ` Mauve halts after first error James Damour 2004-07-05 3:43 ` Stephen Crawley 2004-07-05 6:18 ` Mark Wielaard
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).