Sorry, should also have asked - what symptoms of failure have you seen so far? (Didn't see anything in the JIRA ticket or the code to tell me - getting old, probably blind and missed it).
On 13 February 2011 09:16, Dan Creswell <[email protected]> wrote: > Test program looks fine. > > I'd like to know which JDK's you've run the test on so far please? > > > On 13 February 2011 00:34, Patricia Shanahan <[email protected]> wrote: > >> I have rerun the RIVER-391 failing test, the enhanced version of >> com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td, with >> just the fixes for the synchronization idiom in the QA code. It has not yet >> failed. >> >> That means that the only evidence I have of failures in the outrigger >> FastList is my own test program. I've simplified and stripped down the test >> program, and it still fails. It is attached to RIVER-391 as >> FastListTest.java >> >> I believe it is showing real problems in FastList, so that I should go >> ahead and check in my new version, but I could be mistaken. >> >> I would welcome review of the test program. >> >> Patricia >> > >
