[
https://issues.jboss.org/browse/ISPN-2203?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2203:
------------------------------------
Apparently, if the machine is loaded enough, the delay between successive
{{cache.containsKey(k)}} checks can be > 1s, even though the test does a
{{Thread.sleep(50)}}:
{noformat}
03:20:54.023 TRACE [org.infinispan.interceptors.InvocationContextInterceptor]
(testng-AsyncAPITest) Invoked with command GetKeyValueCommand {key=k, flags=null} and
InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3406e2c6]
03:20:54.026 TRACE [org.infinispan.commands.read.GetKeyValueCommand] (testng-AsyncAPITest)
Found value v5
03:20:55.047 TRACE [org.infinispan.interceptors.InvocationContextInterceptor]
(testng-AsyncAPITest) Invoked with command GetKeyValueCommand {key=k, flags=null} and
InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3bb50d05]
{noformat}
We should probably increase the {{maxIdle}} value from 1s to 2s. Interesting enough, I got
the failure without having trace logging enabled.
Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable
-------------------------------------------------------------------
Key: ISPN-2203
URL:
https://issues.jboss.org/browse/ISPN-2203
Project: Infinispan
Issue Type: Bug
Reporter: Galder ZamarreƱo
Assignee: Mircea Markus
Labels: testsuite_stability
Fix For: 5.2.0.Beta2, 5.3.0.Beta2, 6.0.0.Alpha2
Attachments: AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle.tar.gz,
testAsyncMethodWithLifespanAndMaxIdle-0.log
Test being disabled as part of ISPN-2196 cos it's unstable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira