harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunrong lai" <chunrong...@gmail.com>
Subject Re: [testing][concurrent] Should we exclude failing concurrent tests?
Date Fri, 31 Oct 2008 15:55:52 GMT
+1.
In my experiments RI also has intermitent error for
AbstractQueuedSynchronizerTest, ReentrantLockTest ,
ReentrantReadWriteLockTest .
I also filed HARMONY-6001 for one reproducible Harmony error not happened in
RI.
Anyway I agree to exclude the tests.

On Fri, Oct 31, 2008 at 11:43 PM, Sian January
<sianjanuary@googlemail.com>wrote:

> IIRC the concurrent tests have only recently been included in the
> normal class library test suite, so the failures we are seeing are due
> to missing functionality rather than regressions.  If that's right,
> should we exclude them in the short term and raise a JIRA to track the
> issue?
>
> According to the integrity testing page the classes with failures on
> Windows are:
>
> AbstractQueuedSynchronizerTest
> ThreadLocalTest
> ReentrantLockTest
> ExecutorsTest
> ScheduledExecutorTest
>
> and on Linux are:
>
> ExecutorsTest
> ThreadLocalTest
>
>
> --
> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message