[
https://issues.jboss.org/browse/ISPN-5597?page=com.atlassian.jira.plugin....
]
Sanne Grinovero updated ISPN-5597:
----------------------------------
Description:
I just identified ARQ-1964 while debugging a clustered issue, and I think this affects
the reliability of many tests in Infinispan.
The essence is that while you might think you're testing things on containers \{A,B\},
and so doing able to verify the cross-node synchronisations, you're actually always
testing couples \{A,A\} or \{B,B\}. It's possible that some things actually don't
work as expected even if the tests are passing.
was:
I just identified ARQ-1964 while debugging a clustered issue, and I think this affects
the reliability of many tests in Infinispan.
The essence is that while you might think you're testing things on containers {A,B},
and so doing able to verify the cross-node synchronisations, you're actually always
testing couples {A,A} or {B,B}. It's possible that some things actually don't work
as expected even if the tests are passing.
Verify if clustered Arquillian based tests are really clustered
---------------------------------------------------------------
Key: ISPN-5597
URL:
https://issues.jboss.org/browse/ISPN-5597
Project: Infinispan
Issue Type: Task
Components: Test Suite - Core, Test Suite - Query, Test Suite - Server
Reporter: Sanne Grinovero
Priority: Critical
I just identified ARQ-1964 while debugging a clustered issue, and I think this affects
the reliability of many tests in Infinispan.
The essence is that while you might think you're testing things on containers
\{A,B\}, and so doing able to verify the cross-node synchronisations, you're actually
always testing couples \{A,A\} or \{B,B\}. It's possible that some things actually
don't work as expected even if the tests are passing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)