Re: tests failing w/ illegal access error

2004-04-21 Thread Steve Loughran
Stefan Bodewig wrote: On Tue, 20 Apr 2004, Steve Loughran [EMAIL PROTECTED] wrote: Anyone else seen this? Something like this in strange classloader setups. Are you forking junit? Are parts of Ant or build/classes or build/testcases on your CLASSPATH? You get a method like this when a class

Re: tests failing w/ illegal access error

2004-04-21 Thread Stefan Bodewig
On Wed, 21 Apr 2004, Steve Loughran [EMAIL PROTECTED] wrote: This is me running build.sh test or ant test from ant CVS_HEAD; CLASSPATH is empty. or should be. I will take a look. CLASSPATH points to lib/optional/junit.jar, Sun's JDK 1.4.2_04 on RedHat 7.3 (yes, outdated, I know), no problems.

Re: tests failing w/ illegal access error

2004-04-21 Thread Peter Reilly
Steve Loughran wrote: This is me running build.sh test or ant test from ant CVS_HEAD; CLASSPATH is empty. or should be. I will take a look. Did you do rm -rf bootstrap build before doing ./build.sh test Peter - To unsubscribe,

Re: tests failing w/ illegal access error

2004-04-21 Thread Steve Loughran
Peter Reilly wrote: Steve Loughran wrote: This is me running build.sh test or ant test from ant CVS_HEAD; CLASSPATH is empty. or should be. I will take a look. Did you do rm -rf bootstrap build before doing ./build.sh test not the bootstrap, but I just did that and got the same result. hmmm.

tests failing w/ illegal access error

2004-04-20 Thread Steve Loughran
Anyone else seen this? [junit] Testcase: testDuplicateTargetsImport(org.apache.tools.ant.ProjectTes t): Caused an ERROR [junit] tried to access method org.apache.tools.ant.BuildFileTest.expectLog( Ljava/lang/String;Ljava/lang/String;)V from class org.apache.tools.ant.ProjectTe st

Re: tests failing w/ illegal access error

2004-04-20 Thread Matt Benson
Never seen anything like it... but am I crazy here? I thought Ljava/lang/String would be referring to a String[], but there is no such method void expectLog(String[], String[]), only void expectLog(String, String). If I am not mistaken about the significance of the L, I suppose this would be

RE: tests failing w/ illegal access error

2004-04-20 Thread Dominique Devienne
From: Matt Benson [mailto:[EMAIL PROTECTED] I thought Ljava/lang/String would be referring to a String[], but there is no such method void expectLog(String[], String[]), only void expectLog(String, String). If I am not mistaken about the significance of the L, I suppose this would be

RE: tests failing w/ illegal access error

2004-04-20 Thread Matt Benson
--- Dominique Devienne [EMAIL PROTECTED] wrote: From: Matt Benson [mailto:[EMAIL PROTECTED] I thought Ljava/lang/String would be referring to a String[], but there is no such method No Ljava/lang/String; is String, whereas [Ljava/lang/String; is String[]. --DD Gotcha, thanks. -Matt

tests failing

2003-03-10 Thread Steve Loughran
i have been lax on running tests for a while; now I am seeing (on winXP, single CPU) :- Testcase: testCreateWithEmptyFileset(org.apache.tools.ant.taskdefs.JarTest Caused an ERROR null java.lang.NullPointerException at org.apache.tools.ant.taskdefs.Zip.isEmpty(Zip.java:1082) at

Re: tests failing

2003-03-10 Thread Stefan Bodewig
On Sun, 9 Mar 2003, Steve Loughran [EMAIL PROTECTED] wrote: i have been lax on running tests for a while; now I am seeing (on winXP, single CPU) Is this from CVS HEAD? Looks like the bug Nico's patch was supposed to fix (i.e.

Re: tests failing

2003-03-10 Thread Antoine Levy-Lambert
I also have the tests failing under Windows 2000/Cygwin Amazingly, the tests work if I start them from a debugger where I have written a small wrapper to run the main ant build script with target=run-single-test-only The tests also work from the debugger if I directly invoke

Re: tests failing : red herring

2003-03-10 Thread Antoine Levy-Lambert
Now I found the culprit for these failing tests. I was starting the tests on the cygwin prompt with ./build.sh run-single-test It seems that the tests were then done with the bootstrap directory, which was old. I removed my bootstrap directory, rebuilt everything, and now everything is fine. Yours