[JBoss JIRA] (ISPN-10086) AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10086?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10086:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
> ------------------------------------------------------------------------------
>
> Key: ISPN-10086
> URL: https://issues.jboss.org/browse/ISPN-10086
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.4.11.Final, 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta4, 9.4.14.Final
>
>
> When running tests in parallel, the remote request may complete before the thread that sent the request resumes. Because the scheduled executor is mocked to return {{null}}, this leads to a {{NullPointerException}}:
> {noformat}
> 09:43:41,995 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException
> java.lang.NullPointerException: null
> at org.infinispan.remoting.transport.AbstractRequest.setTimeoutFuture(AbstractRequest.java:94) ~[classes/:?]
> at org.infinispan.remoting.transport.AbstractRequest.setTimeout(AbstractRequest.java:55) ~[classes/:?]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeCommand(JGroupsTransport.java:831) ~[classes/:?]
> at org.infinispan.manager.impl.AllClusterExecutor.submitConsumer(AllClusterExecutor.java:182) ~[classes/:?]
> at org.infinispan.manager.ClusterExecutor.submitConsumer(ClusterExecutor.java:116) ~[classes/:?]
> at org.infinispan.manager.Test$17.call(AllClusterExecutorTest.java:402) ~[test-classes/:?]
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1601) ~[test-classes/:?]
> at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:382) ~[test-classes/:?]
> {noformat}
> The problem may be that the test calls {{Mockito.verify()}} from the consumer twice, once for each node, instead of doing it only on the remote node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-9643) Improve Jacoco support for Infinispan
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9643?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9643:
--------------------------------
Summary: Improve Jacoco support for Infinispan (was: Jacoco support for Infinispan)
> Improve Jacoco support for Infinispan
> -------------------------------------
>
> Key: ISPN-9643
> URL: https://issues.jboss.org/browse/ISPN-9643
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Diego Lovison
> Priority: Major
>
> The jacoco should support IT ( Integration Tests ) and UT ( Unit Tests ).
> Infinispan has a mix of tests, in the same project, we have junit and testng.
> We should be able to generate jacoco-ut.exec and jacoco-it.exec
> During this task, there is the opportunity to merge, remove surefire and failsafe plugin from sub-projects
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-10230) Remove org.infinispan.atomic implementations and MergeOnStore
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/ISPN-10230?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on ISPN-10230:
-------------------------------------
[~dan.berindei] FYI, we are not using these.
> Remove org.infinispan.atomic implementations and MergeOnStore
> -------------------------------------------------------------
>
> Key: ISPN-10230
> URL: https://issues.jboss.org/browse/ISPN-10230
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta4
>
>
> We should remove AtomicMap and FineGrainedAtomicMap as their implementation requires several workarounds that make parts of the codebase very fragile. As AtomicMaps and AtomicMapLookup are not documented in the user guide, the fallout from this should be minimal.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-10234) Remove SingletonCacheWriter
by Will Burns (Jira)
Will Burns created ISPN-10234:
---------------------------------
Summary: Remove SingletonCacheWriter
Key: ISPN-10234
URL: https://issues.jboss.org/browse/ISPN-10234
Project: Infinispan
Issue Type: Sub-task
Reporter: Will Burns
SingletonCacheWriter has been replaced by shared stores as primary owner does writes instead of the coordinator.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-9715) Update internal embedded listeners to be non blocking
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9715?page=com.atlassian.jira.plugin.... ]
Will Burns reassigned ISPN-9715:
--------------------------------
Assignee: Will Burns
> Update internal embedded listeners to be non blocking
> -----------------------------------------------------
>
> Key: ISPN-9715
> URL: https://issues.jboss.org/browse/ISPN-9715
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Listeners
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
>
> With ISPN-9714 it will be possible to have a listener perform non blocking operations. Also any listener that doesn't return a CompletionStage is invoked in a different thread. We should convert all of our internal listeners to return a CompletionStage if they can, so that we don't have to incur the cost of switching threads to execute them.
> We need to ensure that all embedded listeners return a CompletionStage and never block the current thread.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-9715) Update internal embedded listeners to be non blocking
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9715?page=com.atlassian.jira.plugin.... ]
Will Burns updated ISPN-9715:
-----------------------------
Status: Open (was: New)
> Update internal embedded listeners to be non blocking
> -----------------------------------------------------
>
> Key: ISPN-9715
> URL: https://issues.jboss.org/browse/ISPN-9715
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Listeners
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
>
> With ISPN-9714 it will be possible to have a listener perform non blocking operations. Also any listener that doesn't return a CompletionStage is invoked in a different thread. We should convert all of our internal listeners to return a CompletionStage if they can, so that we don't have to incur the cost of switching threads to execute them.
> We need to ensure that all embedded listeners return a CompletionStage and never block the current thread.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months
[JBoss JIRA] (ISPN-10086) AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10086?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10086:
------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/6808, https://github.com/infinispan/infinispan/pull/6809, https://github.com/infinispan/infinispan/pull/6913, https://github.com/infinispan/infinispan/pull/6976 (was: https://github.com/infinispan/infinispan/pull/6808, https://github.com/infinispan/infinispan/pull/6809, https://github.com/infinispan/infinispan/pull/6913)
> AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
> ------------------------------------------------------------------------------
>
> Key: ISPN-10086
> URL: https://issues.jboss.org/browse/ISPN-10086
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.4.11.Final, 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta4, 9.4.14.Final
>
>
> When running tests in parallel, the remote request may complete before the thread that sent the request resumes. Because the scheduled executor is mocked to return {{null}}, this leads to a {{NullPointerException}}:
> {noformat}
> 09:43:41,995 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException
> java.lang.NullPointerException: null
> at org.infinispan.remoting.transport.AbstractRequest.setTimeoutFuture(AbstractRequest.java:94) ~[classes/:?]
> at org.infinispan.remoting.transport.AbstractRequest.setTimeout(AbstractRequest.java:55) ~[classes/:?]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeCommand(JGroupsTransport.java:831) ~[classes/:?]
> at org.infinispan.manager.impl.AllClusterExecutor.submitConsumer(AllClusterExecutor.java:182) ~[classes/:?]
> at org.infinispan.manager.ClusterExecutor.submitConsumer(ClusterExecutor.java:116) ~[classes/:?]
> at org.infinispan.manager.Test$17.call(AllClusterExecutorTest.java:402) ~[test-classes/:?]
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1601) ~[test-classes/:?]
> at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:382) ~[test-classes/:?]
> {noformat}
> The problem may be that the test calls {{Mockito.verify()}} from the consumer twice, once for each node, instead of doing it only on the remote node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 12 months