Alexei, Yes, there are intrmittent failures on both lnx ia32, ia64. I've updated https://issues.apache.org/jira/browse/HARMONY-1979
Thanks, Tanya On 3/20/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote:
Tatyana, As far as I understand these failures are intermittent, right? Regards, 2007/3/20, tatyana doubtsova <[EMAIL PROTECTED]>: > Alexei, > > I've observed some failures after clean-up and updated 1979: > > java.awt.AccessibleAWTWindowTest > java.awt.TextComponentTest hangs or crashes VM > > On lnx ia64 > java.awt.AccessibleAWTButtonTest crashes VM. > > Everything OK on win XP. > > Could you, please update x-lists? > > Thanks, > Tanya > > > > On 3/16/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > > Done. Thanks Vladimir. > > > > 2007/3/16, Vladimir Ivanov <[EMAIL PROTECTED]>: > > > The test java.awt.font.LineBreakMeasurerTest failed on x86-64 Linux. > > > Could you exclude it again? > > > > > > thanks, Vladimir > > > > > > On 3/16/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > > > > > Recently I've discovered that a lot of tests from our AWT exclude > > > > lists are passing tests indeed. We have an old JIRA describing this > > > > problem – HARMONY-1979. So two days ago I've started a big exclude > > > > list cleanup process and just have finished it – see the revision > > > > 518922. According to JUnit report now we have +292 enabled tests on > > > > Windows and +166 on Linux. However, regardless of the fact that I've > > > > tested everything many times on DLRVM & IBM VME on Linux 32/ Windows > > > > 32 it may happen that some of enabled tests will fail / crash on the > > > > configurations that differ from mine. Hope CC will alert us if this is > > > > the case. Please note that I didn't check 64bit builds due the lack of > > > > time. Just assumed the all tests that fail on Linux 32 will fail on > > > > Linux 64 as well. > > > > > > > > In other words, new AWT unit tests failures are possible. It is > > > > normal. Please feel free to send your complaints to this thread. :) > > > > > > > > Thanks, > > > > -- > > > > Alexei Zakharov, > > > > Intel ESSD > > > > > > -- > > Alexei Zakharov, > > Intel ESSD > > > -- Alexei Zakharov, Intel ESSD
