[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10855?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10855:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> MultipleCacheManagersTest factory issues are ignored
> ----------------------------------------------------
>
> Key: ISPN-10855
> URL: https://issues.redhat.com/browse/ISPN-10855
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 9.4.16.Final, 10.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> TestNG doesn't like exceptions being thrown from {{@Factory}} methods, so when {{MultipleCacheManager.defaultFactory()}} finds a problem with the concrete {{factory()}} implementation or with the annotations it replaces the test instance with a {{TestFrameworkFailure}}.
> Turns out that doesn't actually work: TestNG ignores the {{TestFrameworkFailure}} instance and runs the tests on a "default instance" of the test class. This is ok when the problem is the concrete class didn't override {{factory()}} and very likely the test author wanted a single test instance, but it's not ok for other errors like {{factory()}} being copy-pasted from super with the wrong class name.
> We can make TestNG report our factory failures if we implement {{IInstanceInfo}} and mock all the test/configuration methods to throw our exception. We just need to make all configuration methods non-final so we can mock them.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10881?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10881:
------------------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #36, DataGrid Sprint #37)
> Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
> ----------------------------------------------------------------
>
> Key: ISPN-10881
> URL: https://issues.redhat.com/browse/ISPN-10881
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 10.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name.
> Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10824) Hanged tests are ignored by Jenkins
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10824?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10824:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Hanged tests are ignored by Jenkins
> -----------------------------------
>
> Key: ISPN-10824
> URL: https://issues.redhat.com/browse/ISPN-10824
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> ISPN-10161 was supposed to add a custom JUnit report in {{RunningTestsRegistry}} just before killing the JVM. Unfortunately it only calls {{TestSuiteProgress.fakeTestFailure()}}, which sounds like it should do it, but actually only writes a {{Test failed:}} messsage to the console, which Jenkins ignores.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10885) REST Reindex action
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10885?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10885:
------------------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #36, DataGrid Sprint #37)
> REST Reindex action
> -------------------
>
> Key: ISPN-10885
> URL: https://issues.redhat.com/browse/ISPN-10885
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Querying, REST
> Affects Versions: 10.0.1.Final
> Reporter: Tristan Tarrant
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> The Cache rest resource should implement a /rest/v2/caches/{cacheName}?action=reindex&mode=[sync|async]
> The method should return a 200 OK for sync and 202 Accepted for async reindex. It should also not initiate a new reindexing if one is running already and return 409 Conflict.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10888) Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10888?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10888:
------------------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #36, DataGrid Sprint #37)
> Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-10888
> URL: https://issues.redhat.com/browse/ISPN-10888
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache.
> In these cases do not add both, just one.
> Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _'
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10821) Decrease GMS join_timeout and increase xPING num_discovery_runs
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10821?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10821:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Decrease GMS join_timeout and increase xPING num_discovery_runs
> ---------------------------------------------------------------
>
> Key: ISPN-10821
> URL: https://issues.redhat.com/browse/ISPN-10821
> Project: Infinispan
> Issue Type: Task
> Components: Configuration
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Our default JGroups configurations have a GMS {{join_timeout="5000"}}, meaning the first node to start will always wait for 5 seconds before becoming coordinator. It should be safe to use the JGroups default of 2 seconds.
> To make it even more safe, we could configure the discovery protocol's {{num_discovery_runs="3"}}, so that it makes multiple attempts to contact existing nodes during those 2 seconds of waiting. {{num_discovery_runs}} is only used for the initial discovery, so there's no danger of creating additional traffic while the node is up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10807) Don't include Narayana in the server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10807?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10807:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Don't include Narayana in the server
> ------------------------------------
>
> Key: ISPN-10807
> URL: https://issues.redhat.com/browse/ISPN-10807
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server, Transactions
> Affects Versions: 10.0.0.CR3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The Hot Rod tx implementation uses the embedded TM only. Including Narayana in the server distribution is therefore pointless. It should be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10804?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10804:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> JCache tck-runner does not run interception tests
> -------------------------------------------------
>
> Key: ISPN-10804
> URL: https://issues.redhat.com/browse/ISPN-10804
> Project: Infinispan
> Issue Type: Bug
> Components: JCache, Test Suite
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors.
> But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10806) Default semantic configurations for the server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10806?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10806:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Default semantic configurations for the server
> ----------------------------------------------
>
> Key: ISPN-10806
> URL: https://issues.redhat.com/browse/ISPN-10806
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Server
> Affects Versions: 10.0.0.CR3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> org.infinispan.VOLATILE (same as DIST_SYNC)
> org.infinispan.PERSISTENT (VOLATILE + soft index store)
> org.infinispan.INDEXED (PERSISTENT + indexed)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months