harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregory Shimansky <gshiman...@apache.org>
Subject Re: [testing] second M5 candidate (r629320) testing status.
Date Fri, 22 Feb 2008 13:13:18 GMT
Stepan Mishura said the following on 22.02.2008 8:13:
> Hi all,
> 
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
> 
> Please add your comments and clarifications.
> 
> 1) Classlib:
> 
> 5 failures in text module because of HARMONY-5465
> 
> Status: Tony investigated it - not bug difference?
> 
> • Windows_x86_64:
>    1 additional failure in pack200 (not regression)
> 
> 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
> 
> 3) DRLVM regression tests:
> • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206

This is a bug that was never actually fixed. Looking at it, it was 
discovered even in M3. It is an intermittent problem with volatile 
fields and it is not a regression.

> 4) DRLVM tests:
> • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> intermittent)
> 
> Status: according to Vladimir Beliaev this one is not critical and
> should not block the release
> 
> 5) EUTs:
> • Windows x86: 3 failures
> 
> 6) EGAx48:
> • Windows_x86: failed
> • Linux_x86: in progress (passed on the previous snapshot)
> • Linux x86 64: failed
> 
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
> 
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
>        + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
> 
> 8) Functional:
> • On all platfroms:
>    api.java.security.F_KeyFactoryTest_01:
>      HARMONY-4857 - regression introduced in M3. Bug in third-party component
>    api.java.beans.beancontext.BeanContextTest
>      regression caused by changes in locale data
>    api.java.util.jar.Manifest
>      regression introduced by the fix of HARMONY-5473
>    api.java.text.MessageFormat
>      regression caused by migration to ICU HARMONY-5430
> 
> 
> • Windows_x86: +1 failures
>   jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
> 
> • Linux_x86: +4 failures
>    functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> (intermittent?)
>    vm.cli.verbose - regression
>    vm.cli.verbose.verbose01 - regression
>    vm.cli.Xverbose.Xverbose07 - regression
> 
> • Windows_x86_64: +8 failures
>    jit.HLO.devirt.Runtime.RuntimeExtend1
>      not regression
>    jit.HLO.inline.ControlFlow.IfElse.IfElse1
>      regression since M3,looked intermittent in M4 but it stably fails
>    jit.HLO.peel.Switch -intemittent(?)
>    jpda.jdwp.scenario.EB01 - regression
>    jpda.jdwp.scenario.ST07 - regression
>    reg.vm.btest5717
>      regression since M3, looked intermittent in M4 but it stably fails
>    reg.vm.btest6353
>      failed on M3 too, (Andrey said might be issue with the test)
>    reg.vm.btest7214
>      regression since M3, looked intermittent in M4 but it stably fails
> 
> • Linux_x86_64: +12 failures
>    intermittent(?)
>    api.java.io.ObjectOutputStream.writeObjectReadObject0010
>    api.java.io.ObjectOutputStream.writeObjectReadObject0029
>    api.java.io.PushBackInputStream
>    api.java.lang.ref.F_PhantomReferenceTest_03
>    api.java.lang.ref.F_SoftReferenceTest_03
>    api.java.util.logging.Handler
>    vm.cli.verbose.verbose
> 
>    regression:
>    jpda.jdwp.scenario.EB01
>    jpda.jdwp.scenario.ST07
>    reg.jit.btest4318
>    vm.cli.verbose.verbose01
> 
>    reg.vm.btest6353
>      failed on M3 too, (Andrey said might be issue with the test?)
> 
> 9) Geronimo Unit Tests
> 
> • Windows_x86_64: 4 failures
>     org.apache.geronimo.cxf - intermittent(?)
> 
> • Linux_x86_64: 2 failures
>     org.apache.geronimo.cxf - intermittent(?)
> 
> 10) Reliability:
> 
> • Windows_x86:2 failures
>   api.net.DatagramTest - HARMONY-5531
>   api.serialization.SerializableClassesTest- HARMONY-5532
> 
> • Linux_x86: 3 failures
>   api.net.DatagramTest - HARMONY-5531
>   api.serialization.SerializableClassesTest- HARMONY-5532
>   api.text.DecimalFormat_Locales - intermittent(?)
> 
> • Linux x86 64 bit:
>   vm.classloading.ClassCastTest - failed on M4 too
>   api.kernel.thread.ThreadLocalTest - regression
> 
> 11) Stress: need investigation
> • Windows_x86: 1 failure
>   gc.frag.FragmentationFinalizer - intermittent(?)
> 
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
>   gc.frag.Fragmentation
>   gc.frag.FragmentationFinalizer
>   gc.frag.FragmentationReference
> 
> • Windows_x86_64: 4 failures
>   classloader.NotSynchThreads.SupIntf - regression
>   gc.frag.FragmentationFinalizer: HARMONY-5159
>   jpda.jdwp.scenario.MEMORY001 - failed on M4 too
>   jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> 
> • Linux_x86_64: 2 failures
>   jpda.jdwp.scenario.MEMORY001 - failed on M4 too
>   jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> 
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
> 
> 13) VTS VM:
> • Windows_x86_64 & Linux_x86_64
>    vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
>      HARMONY-5347(regression) won't be fixed in M5


-- 
Gregory



Mime
View raw message