[
https://issues.jboss.org/browse/ISPN-8067?page=com.atlassian.jira.plugin....
]
William Burns updated ISPN-8067:
--------------------------------
Description:
http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or...
shows the failure.
What happens is a RemoveExpired command from the testFilteringInCluster test can be seen
in a later test. This is because testFilteringInCluster does not wait for the expiration
event to be sent, because it is filtered out, so there is no way to tell when it is
actually invoked.
The easiest way to fix may be to just add another listener that waits for the entry to
expire, thus making sure the event doesn't occur on another test.
was:
http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or...
shows the failure.
What happens is a RemoveExpired command from the testFilteringInCluster test can be seen
in a later test. This is because testFilteringInCluster does not wait for the expiration
event to be sent, because it is filtered out, so there is no way to tell when it is
actually invoked.
ClientClusterExpirationEventsTest.testSimpleExpired random failures
-------------------------------------------------------------------
Key: ISPN-8067
URL:
https://issues.jboss.org/browse/ISPN-8067
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Reporter: William Burns
Assignee: William Burns
Attachments: testSimpleExpire.zip
http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or...
shows the failure.
What happens is a RemoveExpired command from the testFilteringInCluster test can be seen
in a later test. This is because testFilteringInCluster does not wait for the expiration
event to be sent, because it is filtered out, so there is no way to tell when it is
actually invoked.
The easiest way to fix may be to just add another listener that waits for the entry to
expire, thus making sure the event doesn't occur on another test.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)