Thanks for the sharing. It is strange that I did not observe the unpack200 failures. Other classlib failures are not new. The guity commit of the management failures has been identified as r644719. The issues in jdktools-test are "timeouts" in our testing. They are not new either. Moreover the standalone running, for example "java -cp "/home/laichunrong/apache-ant-1.6.5/lib/junit.jar:./infra/build/checkouts/jdktools/build/tests/classes/" org.apache.harmony.jpda.tests.jdwp.MultiSession.ResumeTest" just report "OK" here (should set LD_LIBRARY_PATH to include ./infra/build/checkouts/jdktools/modules/jpda/src/main/native/jdwp/unix/transport). So I do not think that they are blockers for now. Thanks.
On 8/18/08, Nathan Beyer <[EMAIL PROTECTED]> wrote: > > -1 I'm not able to reproduce the same results on x86_64 Ubuntu Hardy > > Here are the failures I'm seeing, consistently, in classlib-test. The > unpack200 test failures concern me. > > error testGetAttribute > org.apache.harmony.lang.management.MemoryPoolMXBeanImplTest > error testGetCollectionUsage > > org.apache.harmony.lang.management.tests.java.lang.management.MemoryPoolMXBeanTest > failure testWithSql > org.apache.harmony.unpack200.tests.ArchiveTest > failure > testHelloWorld org.apache.harmony.unpack200.tests.SegmentTest > failure test_impliesLjava_security_Permission > tests.api.java.security.PermissionCollectionTest > > Here are the failures I'm seeing, consistently, in jdktools-test. > > error testDebuggerLaunch001 > > org.apache.harmony.jpda.tests.jdwp.DebuggerOnDemand.OnthrowDebuggerLaunchTest > error testDebuggerLaunch002 > > org.apache.harmony.jpda.tests.jdwp.DebuggerOnDemand.OnthrowDebuggerLaunchTest > error testDebuggerLaunch003 > > org.apache.harmony.jpda.tests.jdwp.DebuggerOnDemand.OnthrowDebuggerLaunchTest > error testDebuggerLaunch004 > > org.apache.harmony.jpda.tests.jdwp.DebuggerOnDemand.OnthrowDebuggerLaunchTest > error testAttachConnector001 > org.apache.harmony.jpda.tests.jdwp.MultiSession.AttachConnectorTest > error testClearBreakpoint001 > org.apache.harmony.jpda.tests.jdwp.MultiSession.BreakpointTest > error testMethodEvent001 > org.apache.harmony.jpda.tests.jdwp.MultiSession.MethodEntryExitTest > error > testResume org.apache.harmony.jpda.tests.jdwp.MultiSession.ResumeTest > error testThreadEnd001 > org.apache.harmony.jpda.tests.jdwp.MultiSession.ThreadEndTest > error testThreadStart001 > org.apache.harmony.jpda.tests.jdwp.MultiSession.ThreadStartTest > > drlvm-test and drlvm-reg-test are passing. > > -Nathan > > On Fri, Aug 15, 2008 at 8:26 AM, Sian January > <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > > > We have completed a testing cycle for r681495 and evaluated the results > [1]. > > > > There are some test failures, but most of them are either intermittent > > or were also failing in M6. However if anyone thinks any of these > > test failures are blockers and has not yet had a chance to say, please > > speak up now. > > > > Otherwise, shall we declare r681495 as M7? > > > > Thanks, > > > > Sian > > > > > > [1] http://harmony.markmail.org/message/cpfcnslv53doueeg?q= > > > > > > -- > > Unless stated otherwise above: > > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > 3AU > > >
