Tests on powerpc-unknown-linux-gnu

Mark Wielaard mark@klomp.org
Wed Mar 20 16:33:00 GMT 2002


Hi,

On Thu, 2002-03-21 at 01:25, Tom Tromey wrote:
> >>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
> 
> Mark> # of unexpected failures        2
> Mark> The two failures are from Thread_Interrupt which seems to just Abort.
> 
> Can you look at this?
After a make install and rerunning the tests I get:

		=== libjava Summary ===

# of expected passes		2037
# of unexpected failures	4
# of expected failures		18
# of untested testcases		14

So now there are 4 failures:

FAIL: Thread_Interrupt output from source compiled test
FAIL: Thread_Interrupt output from bytecode->native test
FAIL: Thread_Interrupt -O output from source compiled test
FAIL: Thread_Interrupt -O output from bytecode->native test

But they no longer just Abort. They give output:

wait()
interrupted - ok
sleep()
interrupted - ok
Busy waiting
Error: Busy wait was not interrupted.
join()
interrupted - ok

Strangely when I run the program standalone the output is correct.

Making the wait loop bigger seems to solve the "problem" when running
make check:

--- Thread_Interrupt.java	2000/03/23 12:35:44	1.1
+++ Thread_Interrupt.java	2002/03/21 00:23:12
@@ -49,7 +49,7 @@
     System.out.println ("Busy waiting");
 
     int count = 0;
-    for (int i=0; i < 1000000; i++)
+    for (int i=0; i < 3000000; i++)
       {
         Thread.yield();
 	count += 5;

		=== libjava Summary ===

# of expected passes		2041
# of expected failures		18
# of untested testcases		14

Maybe my machine is just to fast :)

Cheers,

Mark



More information about the Java mailing list