[JBoss JIRA] (ISPN-5597) Verify if clustered Arquillian based tests are really clustered
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5597?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-5597:
------------------------------------
There don't seem to be many tests using `@OperateOnDeployment`, but it would be a good idea to change the defaultProtocol to {{Servlet 3.0}} in all {{arquillian.xml}} files.
> 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 - 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)
10 years, 5 months
[JBoss JIRA] (ISPN-5597) Verify if clustered Arquillian based tests are really clustered
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5597?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5597:
-------------------------------
Component/s: (was: Test Suite - Core)
> 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 - 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)
10 years, 5 months
[JBoss JIRA] (ISPN-5597) Verify if clustered Arquillian based tests are really clustered
by Sanne Grinovero (JIRA)
[ 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)
10 years, 5 months
[JBoss JIRA] (ISPN-5597) Verify if clustered Arquillian based tests are really clustered
by Sanne Grinovero (JIRA)
[ 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, so being able to verify the cluster, you're actually always testing 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)
10 years, 5 months
[JBoss JIRA] (ISPN-5597) Verify if clustered Arquillian based tests are really clustered
by Sanne Grinovero (JIRA)
Sanne Grinovero created ISPN-5597:
-------------------------------------
Summary: 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, so being able to verify the cluster, you're actually always testing 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)
10 years, 5 months
[JBoss JIRA] (ISPN-5596) "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache
by Andreas Pabst (JIRA)
Andreas Pabst created ISPN-5596:
-----------------------------------
Summary: "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache
Key: ISPN-5596
URL: https://issues.jboss.org/browse/ISPN-5596
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 7.2.3.Final
Environment: Windows 7
Reporter: Andreas Pabst
When stopping and restarting a cache with SoftIndexFileStore persistence, it behaves strangely.
Calling cache.clear() leads to the following exception:
ERROR: ISPN000136: Execution error
org.infinispan.persistence.spi.PersistenceException: Cannot clear data directory!
at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:234)
at org.infinispan.persistence.manager.PersistenceManagerImpl.clearAllStores(PersistenceManagerImpl.java:372)
at org.infinispan.interceptors.CacheWriterInterceptor.visitClearCommand(CacheWriterInterceptor.java:158)
...
Caused by: java.io.IOException: Cannot delete file soft-index-test\data\2
at org.infinispan.persistence.sifs.FileProvider.clear(FileProvider.java:205)
at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:232)
If the manager is also stopped and recreated every time, this only happens after the third iteration.
Calling cache.remove() in the same place leads to an unrecoverable corruption of the cache store files: java.lang.IllegalArgumentException: Negative position
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months