On 5/17/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
I am afraid it's some threading issue that depends on timing (such as
timedwait). It's interesting to know how RI behaves with those test
cases.
Seems, these tests are runtime dependent. The test
gc.ThreadSuspension, for example, always failed on RI:
--output on RI -------------------
sh run.sh
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
Thu May 17 10:51:15 NOVST 2007
-- starting unsuspendable computation --
-- starting suspendable computation --
forcing gc after 1 s delay
FAIL
-- unsuspendable computation finished --
gc completed
0
------------------------------------
and passed on DRLVM (non-loaded box):
-------output on DRLVM---
sh run.sh
Apache Harmony Launcher : (c) Copyright 1991, 2006 The Apache Software
Foundation or its licensors, as applicable.
java version "1.5.0"
pre-alpha : not complete or compatible
svn = r538790, (May 17 2007), Linux/em64t/gcc 3.3.3, debug build
http://incubator.apache.org/harmony
Thu May 17 10:55:26 NOVST 2007
-- starting unsuspendable computation --
-- starting suspendable computation --
forcing gc after 1 s delay
gc completed
PASS
0
------------------------------------
thanks, Vladimir
Thanks,
xiaofeng
On 5/17/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> On 5/16/07, Gregory Shimansky <[EMAIL PROTECTED]> wrote:
> > Vladimir Ivanov wrote:
> > > Hello everyone,
> > > today I ran the DRLVM smoke tests on the SUSE 9 Linux x86_64 in
> > > parallel with stressing class (run 4 thread with infinite increment
> > > into cycle).
> >
>
> > Do you mean the machine was out of virtual memory? If yes, it is
> > possible that VM crashed on malloc returning NULL, there are many places
> > where pointer returned by malloc is not checked (in debug mode usually
> > there is an assertion, but this assertion is a noop in release).
>
> No, my process load CPU only. I run it as: java -cp . Stress
> ---------------- Stress.java ---------------------------
> public class Stress {
> public static void main(String[] args) {
> Run[] threads = new Run[4];
> for (int i = 0; i < threads.length; i++) {
> threads[i] = new Run();
> threads[i].start();
> }
> while (true){}
> }
> }
> class Run extends Thread {
> public void run() {
> long i = 0;
> try {
> while (true) { i++; }
> } catch (Exception e) {
> System.out.println("Exception:" + e);
> }
> }
> }
> -----------------------------------------------------------------
>
> Results for DRLVM+GCv4:
> "JET" mode
> [echo] Running test : gc.ThreadSuspension
> [echo] *** FAILED **** : gc.ThreadSuspension (0 res code)
>
> [echo] Running test : stress.Sync
> [java] Java Result: 139
> [echo] *** FAILED **** : stress.Sync (139 res code)
>
> "OPT" mode
> [echo] Running test : gc.Force
> [java] Java Result: 139
> [echo] *** FAILED **** : gc.Force (139 res code)
>
> [echo] Running test : gc.ThreadSuspension
> [echo] *** FAILED **** : gc.ThreadSuspension (0 res code)
>
> "DEFAULT" mode
> [echo] Running test : gc.ThreadSuspension
> [echo] *** FAILED **** : gc.ThreadSuspension (0 res code)
>
> [echo] Running test : util.Prop
> [java] Java Result: 139
> [echo] *** FAILED **** : util.Prop (139 res code)
>
> "SERVER" mode
> [echo] Running test : gc.ThreadSuspension
> [echo] *** FAILED **** : gc.ThreadSuspension (0 res code)
>
>
> >
> > It would be useful to enable core dumps and at least look at the stack
> > trace for crashed tests.
> >
> > > I observed following failures (below).
> > >
> > > Could someone look at these results?
> > > Note, I checked the out data for the gc.ThreadSuspension test and
> > > found that out has something like that (out for run in 'server' mode):
> > > <system-out>
> > > -- starting unsuspendable computation --
> > > -- starting suspendable computation --
> > > forcing gc after 1 s delay
> > > gc completed
> > > PASS
> > > </system-out>
> > > <system-err>
> > > SIGSEGV in VM code.
> > > </system-err>
> > >
> > > thanks, Vladimir
> > >
> > > -------- Results -------------------------------------------
> > >
> > > "JET" mode
> > > [echo] Running test : gc.RunFinalizersOnExitTest
> > > [echo] *** FAILED **** : gc.RunFinalizersOnExitTest (0 res code)
> > >
> > > [echo] Running test : gc.ThreadSuspension
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : gc.ThreadSuspension (139 res code)
> > >
> > > [echo] Running test : shutdown.TestLock
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : shutdown.TestLock (139 res code)
> > >
> > > [echo] Running test : stress.Sync
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : stress.Sync (139 res code)
> > >
> > > [echo] Running test : thread.InfiniteFinalizer
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : thread.InfiniteFinalizer (139 res code)
> > >
> > > 'OPT' mode
> > > [echo] Running test : gc.ThreadSuspension
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : gc.ThreadSuspension (139 res code)
> > >
> > > default mode
> > > [echo] Running test : shutdown.TestLock
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : shutdown.TestLock (139 res code)
> > >
> > > [echo] Running test : stress.Sync
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : stress.Sync (139 res code)
> > >
> > > [echo] Running test : thread.InfiniteFinalizer
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : thread.InfiniteFinalizer (139 res code)
> > >
> > > Server mode (not finished yet)
> > > [echo] Running test : gc.RunFinalizersOnExitTest
> > > [echo] *** FAILED **** : gc.RunFinalizersOnExitTest (0 res code)
> > >
> > > [echo] Running test : gc.ThreadSuspension
> > > [java] Java Result: 139
> > > [echo] *** FAILED **** : gc.ThreadSuspension (139 res code)
> > >
> >
> >
> > --
> > Gregory
> >
> >
>
--
http://xiao-feng.blogspot.com
