[infinispan-issues] [JBoss JIRA] (ISPN-1999) Improve stability of testsuite

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694729#comment-12694729 ] 

Galder Zamarreño commented on ISPN-1999:
----------------------------------------

I've added more fixes, but IBM runs are showing interesting problems. For start() methods that have the same priority, ordering varies from one JDK to the other. To be precise, in IBM you see:

{code}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!! (testng-NonStringKeyPreloadTest) Exiting because loaders.jdbc.stringbased.NonStringKeyPreloadTest has NOT shut down all the cache managers it has started !!!!!!!
!!!!!! (testng-NonStringKeyPreloadTest) The still-running cacheManager was created here: org.infinispan.loaders.jdbc.stringbased.NonStringKeyPreloadTest.testPreloadWithKey2StringMapper(NonStringKeyPreloadTest.java:60) !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!{code}

This happens because on IBM, TransactionTable.start() is not executed before the expected the failure, but in Sun it does. The reason for this is cos CacheLoaderManagerImpl.start() is executed before TransactionTable.start() in IBM, whereas in Sun, it happens afterwards.

I need to check with others about start priorities in this particular case.
                
> Improve stability of testsuite
> ------------------------------
>
>                 Key: ISPN-1999
>                 URL: https://issues.jboss.org/browse/ISPN-1999
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Test Suite
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
>
>
> Work related to improving testsuite stability in order to avoid cache managers being left open.
> So far, this particularly affects the Hot Rod testsuite, but might be more changes needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira