[infinispan-issues] [JBoss JIRA] (ISPN-8298) DistAsyncFuncTest.testLockedStreamSetValue random test failure

[William Burns (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Burns updated ISPN-8298:
--------------------------------
    Description: 
Test failure at: http://ci.infinispan.org/job/Infinispan/job/master/144/

Looking at the stack trace, this test failed before it even got to the lock stream. For some reason the async write wasn't completed properly...

It seems the ReplListener was just recently fixed for something similar with L1 invalidations https://github.com/infinispan/infinispan/commit/fb165dc25cba7f26652292a1f9557504ec46881a#diff-71bf0a8d632586ad581b6e38edd5e229 I fear this test in general may not be very deterministic and could fail for any test using it. I would suggest replacing it possibly.

  was:
Test failure at: http://ci.infinispan.org/job/Infinispan/job/master/144/

Looking at the stack trace, this test failed before it even got to the lock stream. For some reason the async write wasn't completed properly...



> DistAsyncFuncTest.testLockedStreamSetValue random test failure
> --------------------------------------------------------------
>
>                 Key: ISPN-8298
>                 URL: https://issues.jboss.org/browse/ISPN-8298
>             Project: Infinispan
>          Issue Type: Bug
>            Reporter: William Burns
>            Assignee: William Burns
>
> Test failure at: http://ci.infinispan.org/job/Infinispan/job/master/144/
> Looking at the stack trace, this test failed before it even got to the lock stream. For some reason the async write wasn't completed properly...
> It seems the ReplListener was just recently fixed for something similar with L1 invalidations https://github.com/infinispan/infinispan/commit/fb165dc25cba7f26652292a1f9557504ec46881a#diff-71bf0a8d632586ad581b6e38edd5e229 I fear this test in general may not be very deterministic and could fail for any test using it. I would suggest replacing it possibly.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)