harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgueni Brevnov" <evgueni.brev...@gmail.com>
Subject Re: [testing] M4 candidate (r603534) testing status.
Date Fri, 14 Dec 2007 10:45:46 GMT
On 12/14/07, Xiao-Feng Li <xiaofeng.li@gmail.com> wrote:
> On Dec 14, 2007 5:44 PM, Evgueni Brevnov <evgueni.brevnov@gmail.com> wrote:
> >
> > On 12/14/07, Xiao-Feng Li <xiaofeng.li@gmail.com> wrote:
> > > I saw this:
> > >
> > > Reliability:
> > > Linux_X86 regression:
> > >   vm.finalization.FinalizeThrowRestoreTest
> > >
> > > I am not sure if anybody has early evaluation  about it. If not, I
> > > will create a JIRA for it.
> > >
> > > Thanks,
> > > xiaofeng
> > >
> > > On Dec 14, 2007 4:09 PM, Stepan Mishura <stepan.mishura@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > Please see testing status[1] for r603534 below.
> > > > Note to my comments:
> > > > - I marked tests as regression if they passed on M3 [2]
> > > > - I question tests as intermittent if they passed on the previous
> > > > snapshot (r603433) [3]
> > > > - There are some tests that failed on M3 too. (move them to the exclude
lists?)
> > > > - Not all failures have JIRA issue assigned so please help me to find
> > > > related JIRA number (if there is any).
> > > >
> > > > All comments and clarifications are greatly appreciated!
> > > >
> > > > =====================================================
> > > > We have the next suites failed on the snapshot.
> > > >
> > > > * Eclipse Unit Tests 3.3
> > > >    - Linux_x86: 4 failures
> > > >    - Windows_x86: pass rate 96.92%
> > > >    - Linux_x86_64: pass rate 95.29%
> > > >
> > > > Would be nice to get failures evaluation.
> > > > We definitely improved stability of the Eclipse Unit Test suite since
> > > > M3 (Thanks to Vladimir Beliaev).
> > > > But the are still some issues such as intermittent suite crashes (that
> > > > make me very upset).
> > > >
> > > > * EGAx48:
> > > >    - Linux_x86 & Linux_x86_64 : failed. (HARMONY-5250 / regression?)
> > > >    - Windows_x86:
> > > >       Still no status – the scenario causes CC host down after running
> > > > several hours.
> > > >       Currently I can not figure out if this is the host's issue or
> > > > problem introduced by Harmony.
> > > >
> > > >
> > > > * EHWA(GUI)
> > > >    - Linux_x86 & Linux_x86_64 : failed.
> > > >    The scenario is quite unstable. Most probably I'll drop the
> > > > scenario in M5 from snapshot test and use only EHWA-API.
> > > >
> > > >
> > > > * Functional:
> > > >       F_KeyFactoryTest_01: regression on all platforms (HARMONY-4857)
> > > >
> > > >   - Linux_x86:
> > > >       JComponent: intermittent?
> > > >   - Linux_x86_64:
> > > >       btest6353: fails on M3 too
> > > >   - Windows_x86_64:
> > > >       DataOutputStream, writeObjectReadObject0004, IfElse1, btest5717,
> > > > btest7214 : intermittent?
> > > >       btest6353: fails on M3 too
> > > >
> > > > * GUT:
> > > >     ContainerTest, JAASSecurityTest - fail on all platforms
> > > >       HARMONY-4895 says that this bug in Geronimo and not a regression.
> > > >
> > > >   - Linux_x86:
> > > >     HARMONY-5302 - says that this a bug in tests (I don't understand
> > > > then why they passed on M3)
> > > >     security\jaas\ConfigurationEntryTest
> > > >     security\jaas\LoginKerberousNonGeronimoTest
> > > >     security\jaas\LoginKerberousTest
> > > >     security\jaas\LoginSQLTest
> > > >     security\network\protocol\SubjectCarryingProtocolTest
> > > >     security\remoting\jmx\RemoteLoginTest
> > > >
> > > >   - Linux_x86_64:   53 failures (11 on M3)
> > > >   - Windows_x86_64: 22 failures (28 on M3)
> > > >
> > > >
> > > > * JDKTools
> > > >   - Windows_x86_64: 3 failures by TimeoutException.
> > > >   Regression? I previously incorrectly reported that they are
> > > > intermittent. They stably fail on M4 builds.
> > > >
> > > > * Reliability
> > > >
> > > >     Failed on x86 platforms but they also failed on M3
> > > >     api.net.HttpConnectionTest (I wonder why HARMONY-5266 didn't fixed
it)
> > > >     api.net.SingleConnectTest
> > > >
> > > >   - Linux_x86:
> > > >
> > > >     Regresions:
> > > >     api.kernel.object.ObjectFinalizeTest
> > > >     api.kernel.throwable.StackTraceExcptsTest
> > > >     api.text.DecimalFormat_Locales
> > > >     api.zip.ZipEntryIterateThreadingTest
> > > >     api.zip.ZlibTest
> > > >     vm.finalization.FinalizeThrowRestoreTest
> > > >     vm.stack.StackUnwindTest
> > > >
> > > >     They also failed on M3:
> > > >     api.nio.channels.filechannel.FileChannelMapTest
> > > >     api.nio.channels.filechannel.MappedByteBufferForceTest
> > > >     api.serialization.SerializableClassesTest
> > > >
> > > >   - Windows_x86
> > > >
> > > >     Regresions:
> > > >     api.kernel.string.InternThreadingTest - regression
> > > >     api.kernel.thread.Calculation.CalcTest
> > > >     api.kernel.thread.RecursiveThreadTest
> > > >     api.kernel.thread.StackTraceTest
> > > >     api.kernel.thread.Synchronization
> > > >     api.kernel.thread.ThreadArrayTest
> > > >     api.kernel.threadgroup.EnumerateTest
> > > >     api.net.DatagramTest
> > > >     api.serialization.SerializableClassesTest
> > > >     vm.stack.StackUnwindTest
> > > >
> > > >   - Linux_x86_64:
> > > >
> > > >     Regressions:
> > > >     vm.classloading.ClassCastTest
> > > >
> > > > * Stress
> > > >
> > > >   - Linux_x86:
> > > >     StackUnwindingManyObjectsTests: 5 fails on M3 too (HARMONY-5158 /
> > > > test issue?)
> > > >     Fragmentation, FragmentationFinalizer, FragmentationReference:
> > > > HARMONY-5159 (wasn't run during M3 so not regression)
> > > >
> > > >   - Windows_x86:
> > > >      StackUnwindingManyObjectsTests: 5 fails on M3 too (HARMONY-5158 /
> > > > test issue?)
> > > >      FragmentationReference: HARMONY-5159 (wasn't run during M3 so not
> > > > regression)
> > > >
> > > >   - Linux_x86_64:
> > > >     jni.arguments,jni.arrays - fails on M3 too so not regression / HARMONY-????
> > > >     MEMORY001, MEMORY003 - HARMONY-5047 (fails on M3 too so not regression)
> > > >
> > > >   - Windows_x86_64:
> > > >     NotSynchThreads.ManyClasses - crash (HARMONY-5003), regression
> > > >     Fragmentation, FragmentationFinalizer, FragmentationReference:
> > > > HARMONY-5159 (wasn't run during M3 so not regression)
> >
> > Hi,
> >
> > Fragmentation & FragmentationFinalizer tests have been enabled in Q4
> > since revision 601041. They made six successfull runs (by CC) since
> > that. Unfortunately last two runs failed with the same stack trace. So
> > we have a regression since revision 603102 (or probably this is
> > intermittent failure).
> >
> > If you look closer at HARMONY-5159 you would realize that this JIRA
> > states another problem which has no relation with current issue.
> >
> > Do we treat it as critical problem for M4?
>
> Evgueni, Do you ask if H5159 is critical or the other issue is
> critical? Probably we should ask JIT people to answer if H5159 is
> critical.

No, I don't ask about H5159. This issue doesn't seems to be connected
to current failures in any way.

> Stepan said it's not a regression.

Yes, this is not a regression since M3. But this is a regression since
revision 603102. These two tests have stably passed for a week until
revision 603433.
These tests crashes with stack trace which I didn't see before:

Windows reported exception: 0xc0000005
Registers:
    RAX: 0x000000001fd28000, RBX: 0x000000001fb30000
    RCX: 0x0000000000000000, RDX: 0x00000000c000012d
    RSI: 0x00000000034c9710, RDI: 0x0000000001ee2280
    RSP: 0x000000000012ca00, RBP: 0x0000000024a30430
    R8 : 0x0000000000000000, R9 : 0x0000000078ec0000
    R10: 0x00000000000001f8, R11: 0x0000000000000246
    R12: 0x00000000034c9710, R13: 0x0000000024a28000
    R14: 0x000000000000409a, R15: 0x0000000044560000
    RIP: 0x0000000001eb87c1
Windows reported exception: 0xc0000005
Registers:
    RAX: 0x0000000024a20430, RBX: 0x000000004596e750
    RCX: 0x000000004596e750, RDX: 0x0000000024a30430
    RSI: 0x000000000012bb00, RDI: 0x0000000000000000
    RSP: 0x000000000012b920, RBP: 0x0000000000000000
    R8 : 0x00007fffffff0000, R9 : 0x000000000012b9b0
    R10: 0x0000000000000000, R11: 0x0000000000000293
    R12: 0x0000000000000001, R13: 0x0000000045812820
    R14: 0x0000000000000000, R15: 0x00000000ffffffff
    RIP: 0x000000000078d531
Stack trace:
  0: verify_object_header (??:-1)
  1: ?? (??:-1)
  2: org/apache/harmony/test/stress/gc/share/GcTest.freeMemory()J
(GcTest.java:438)
  3: org/apache/harmony/test/stress/gc/share/GcTest.setUpAfterWatchers()V
(GcTest.java:86)
  4: org/punit/method/runner/AbstractMethodRunner.setUpAfterWatchers([Ljava/lang/Object;)V
(??:-1)
  5: org/punit/method/runner/AbstractMethodRunner.run(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/Object;)V
(??:-1)
  6: org/punit/runner/AbstractRunner.runTestMethod(Ljava/lang/Object;Ljava/lang/reflect/Method;)V
(??:-1)
  7: org/punit/runner/AbstractRunner.access$100(Lorg/punit/runner/AbstractRunner;Ljava/lang/Object;Ljava/lang/reflect/Method;)V
(??:-1)
  8: org/punit/runner/AbstractRunner$4.traverse(Ljava/lang/Object;)V (??:-1)
  9: org/punit/util/TraverserUtil.traverse(Ljava/util/Iterator;Lorg/punit/util/Traverser;)V
(??:-1)
 10: org/punit/runner/AbstractRunner.runTestClassImpl(Ljava/lang/Class;)V
(??:-1)
 11: org/punit/runner/AbstractRunner.runTestClass(Ljava/lang/Class;)V (??:-1)
 12: org/punit/runner/AbstractRunner.runTestClasses([Ljava/lang/Object;)V
(??:-1)
 13: org/punit/runner/AbstractRunner.run(Ljava/lang/Class;)I (??:-1)
 14: org/apache/harmony/test/share/stress/AbstractTest.runTestClass()V
(AbstractTest.java:61)
 15: org/apache/harmony/test/stress/gc/share/GcTest.main([Ljava/lang/String;)V
(GcTest.java:73)

Thanks
Evgueni

If you ask about the
> other issue (performance in Linux86), I guess we can only evaluate it
> after the OOME problem is solved, because to me it's hard to expect
> the behavior if the memory is out (without handling) while finalizers
> are under processing.
>
> Thanks,
> xiaofeng
>
> > Thanks
> > Evgueni
> >
> >
> > > >     gc.mem.MemoryTest3 - regression / HARMONY-????
> > > >     jni.stack - fails on M3 too so not regression / HARMONY-????
> > > >     EVENT014- crash (HARMONY-????)/ regression
> > > >     MEMORY001, MEMORY003 - HARMONY-5047 (fails on M3 too so not regression)
> > > >     StressThreads12Test - crash (HARMONY-????)/ regression
> > > >
> > > > * VTS VM
> > > >   - Windows_x86:
> > > >       dstore_20701 - intermittent?
> > > >
> > > > [1] http://people.apache.org/~mloenko/snapshot_testing/script/r603534/index.html
> > > > [2] http://people.apache.org/~mloenko/snapshot_testing/script/r580985/index.html
> > > > [3] http://people.apache.org/~mloenko/snapshot_testing/script/r603433/index.html
> > > >
> > > > Thanks,
> > > > Stepan Mishura
> > > > Intel Enterprise Solutions Software Division
> > > >
> > >
> > >
> > >
> > > --
> > > http://xiao-feng.blogspot.com
> > >
> >
>
>
>
> --
> http://xiao-feng.blogspot.com
>

Mime
View raw message