On 5/14/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
On 5/14/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> On 5/14/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
> > On 5/14/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> > > Sorry, forgot to copy test name:
> > > classlib\trunk\build.xml:169: The following error occurred while
> > > executing this line: classlib\trunk\make\build-test.xml:142: There
> > > were test crashes:
> > >
classlib\trunk\build\test_report\TEST-tests.api.java.nio.charset.CharsetDecoderTest.xml
> >
> > This failure can't be reproduced locally in my machine. Btw, this test
> > doesn't invoke GC actually, so it might be caused by some other
> > components than GC.
> >
>
> > I found the other two intermittent failures: One is the
> > java.lang.ClassGenericsTest in jit/opt mode (more in Linux64); The
> No, it is new for me.
Maybe the failure only happens in Fedora Linux64. It's highly
reproducible actually.
> > other is JVMTI test PopFrame1 with following strange error message:
> > SIGTRAP in VM code.
> > Stack trace:
> > <end of stack trace>
> > This is sometimes reported in Linux32.
>
> Yes, I saw it before. The CC/CI failed on Linux x86 now due to this
> test failure.
> But I can not reproduce it manually yet (
Neither did I. Probably we need file a JIRA for it. Thanks,
issue 3681 was created to track it.
thanks, Vladimir
xiaofeng
> thanks, Vladimir
> >
> > Have you met the similar failures before?
> >
> > Thanks,
> > xiaofeng
> >
> > > On 5/14/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> > > > Thanks!
> > > > Classlib tests passed for me on 3 platforms now. On Win64 classlib
> > > > tests failed due to failure of test:
> > > >
> > > > It is intermittent failure and it is hard to reproduce :(
> > > >
> > > > thanks, Vladimir
> > > >
> > > > On 5/14/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
> > > > > On 5/14/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> > > > > > Hello everybody,
> > > > > > the summary of CC/CI status available at
> > > > > > http://www.harmonytest.org/upload/cc1.html and
> > > > > > http://www.harmonytest.org/upload/cc2.html
> > > > > >
> > > > > > is:
> > > > > > 1) the classlib test test_CtorLjava_io_ByteArrayInputStreamClass
(from
> > > > > > org.apache.harmony.security.tests.asn1.der.BerInputStreamTest)
> > > > > > failed with java.lang.OutOfMemoryError on DRLVM+GCv5 on 4 platforms.
> > > > > > Note this test passed on DRLVM GCv4.1
> > > > >
> > > > > Vladimir, I've reverted a commit that caused the failure. Now it
> > > > > should have no problem.
> > > > >
> > > > > > 2) DRLVM test test_freeMemoryClass (from java.lang.RuntimeTest)
> > > > > > intermittently failed with "junit.framework.AssertionFailedError:
> > > > > > Runtime.freeMemory method should be sensitive to huge memory
> > > > > > allocating!". Issue 3711 was created to track it.
> > > > >
> > > > > This should pass as well after the revert.
> > > > >
> > > > > > 3) DRLVM kernel test testGetContextClassLoader_MainClass (from
> > > > > > java.lang.ThreadTest) intermittently failed on DRLVM with
> > > > > > java.util.NoSuchElementException. Issue 3838 was created to track
it.
> > > > >
> > > > > This one is not related to the reverted commit. It is suspected to be
> > > > > an issue with the association mechanism between native thread and Java
> > > > > thread. Still under investigation.
> > > > >
> > > > > > I suggest excluding these tests up to end of failures evaluation if
> > > > > > this evaluation will take long time (say, more than 1 day).
> > > > > > Is it OK?
> > > > > > thanks, Vladimir
> > > > >
> > > > > Basically I agree to exclude the third one for the moment.
> > > > >
> > > > > Thanks, xiaofeng
> > > > >
> > > > > --
> > > > > http://xiao-feng.blogspot.com
> > > > >
> > > >
> > >
> >
> >
> > --
> > http://xiao-feng.blogspot.com
> >
>
--
http://xiao-feng.blogspot.com
