Re: tests failing w/ illegal access error

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. Ok.

Re: tests failing w/ illegal access error

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, e-m

Re: tests failing w/ illegal access error

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 problem

Re: tests failing w/ illegal access error

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 ? Are parts of Ant or build/classes or build/testcases on your CLASSPATH? You get a method like this when a class tries t

Re: tests failing w/ illegal access error

On Tue, 20 Apr 2004, Steve Loughran <[EMAIL PROTECTED]> wrote: > Anyone else seen this? Something like this in strange classloader setups. Are you forking ? Are parts of Ant or build/classes or build/testcases on your CLASSPATH? You get a method like this when a class tries to invoke a protect

RE: tests failing w/ illegal access error

--- 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, t

RE: tests failing w/ illegal access error

> 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 thi

Re: tests failing w/ illegal access error

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

tests failing w/ illegal access error

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

- Original Message - From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 10, 2003 00:22 Subject: Re: tests failing > On Sun, 9 Mar 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: > > > i have been lax on runnin

Re: tests failing : red herring

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. Your

Re: tests failing

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

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.

tests failing

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 org.