October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9629) Coverage profile is not working

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9629?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9629: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6343 > Coverage profile is not working > ------------------------------- > > Key: ISPN-9629 > URL: https://issues.jboss.org/browse/ISPN-9629 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Priority: Major > > When running the `coverage` profile. The build is failing because > Run: mvn verify -Pcoverage -Dmaven.test.failure.ignore=true > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (copy-generated-classes) on project infinispan-parent: Execution copy-generated-classes of goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies could not be resolved: Failure to find org.apache.ant:ant-nodeps:jar:1.10.1 in http://download.lab.eng.bos.redhat.com/brewroot/repos/jb-dg-7-rhel-7-buil... was cached in the local repository, resolution will not be reattempted until the update interval of mead-jdg7-plugins has elapsed or updates are forced -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9629) Coverage profile is not working

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9629?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9629: -------------------------------- Status: Open (was: New) > Coverage profile is not working > ------------------------------- > > Key: ISPN-9629 > URL: https://issues.jboss.org/browse/ISPN-9629 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Priority: Major > > When running the `coverage` profile. The build is failing because > Run: mvn verify -Pcoverage -Dmaven.test.failure.ignore=true > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (copy-generated-classes) on project infinispan-parent: Execution copy-generated-classes of goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies could not be resolved: Failure to find org.apache.ant:ant-nodeps:jar:1.10.1 in http://download.lab.eng.bos.redhat.com/brewroot/repos/jb-dg-7-rhel-7-buil... was cached in the local repository, resolution will not be reattempted until the update interval of mead-jdg7-plugins has elapsed or updates are forced -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9629) Coverage profile is not working

by Diego Lovison (Jira)

Diego Lovison created ISPN-9629: ----------------------------------- Summary: Coverage profile is not working Key: ISPN-9629 URL: https://issues.jboss.org/browse/ISPN-9629 Project: Infinispan Issue Type: Bug Reporter: Diego Lovison When running the `coverage` profile. The build is failing because Run: mvn verify -Pcoverage -Dmaven.test.failure.ignore=true {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (copy-generated-classes) on project infinispan-parent: Execution copy-generated-classes of goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies could not be resolved: Failure to find org.apache.ant:ant-nodeps:jar:1.10.1 in http://download.lab.eng.bos.redhat.com/brewroot/repos/jb-dg-7-rhel-7-buil... was cached in the local repository, resolution will not be reattempted until the update interval of mead-jdg7-plugins has elapsed or updates are forced -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9500) ConcurrentSmallIntSet.clear() does not always set the size to 0

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9500?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9500: -------------------------------- Labels: on-hold (was: ) > ConcurrentSmallIntSet.clear() does not always set the size to 0 > --------------------------------------------------------------- > > Key: ISPN-9500 > URL: https://issues.jboss.org/browse/ISPN-9500 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3, 9.3.4.Final > > > {{ConcurrentSmallIntSet.clear()}} processes the array values with a loop that stops when {{value <= 0}}. This breaks when the highest bit is set, leaving the set empty but with {{size() > 0}} and {{isEmpty() == false}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7168) Prevent user from configuring passivation with a shared store

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-7168?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-7168. ------------------------------- > Prevent user from configuring passivation with a shared store > ------------------------------------------------------------- > > Key: ISPN-7168 > URL: https://issues.jboss.org/browse/ISPN-7168 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.4.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.0.CR3, 9.4.0.Final > > > Passivation only makes sense with a non shared cache store. --The problem is that if an entry is passivated on a shared cache store only the first node will be able to activate the entry and subsequent nodes will always see null.-- > Looking closer the bigger issue is if an entry becomes passivated and then subsequently written to you will have a different value in the store as you would in memory. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9472) FunctionalMapTest is not executed by suite

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9472?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9472: -------------------------------- Labels: on-hold (was: ) > FunctionalMapTest is not executed by suite > ------------------------------------------ > > Key: ISPN-9472 > URL: https://issues.jboss.org/browse/ISPN-9472 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.0.CR1 > Reporter: Adrian Nistor > Assignee: Dan Berindei > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3 > > > The test is missing from test results. Trying to execute is from IDE results in NPE > {code} > java.lang.NullPointerException > at org.infinispan.test.MultipleCacheManagersTest$TransactionalModeFilter.lambda$new$0(MultipleCacheManagersTest.java:970) > at org.infinispan.test.MultipleCacheManagersTest$AnnotationFilter.lambda$test$0(MultipleCacheManagersTest.java:935) > at java.util.stream.MatchOps$1MatchSink.accept(MatchOps.java:90) > at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) > at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) > at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230) > at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:449) > at org.infinispan.test.MultipleCacheManagersTest$AnnotationFilter.test(MultipleCacheManagersTest.java:935) > at org.infinispan.test.MultipleCacheManagersTest$TransactionalModeFilter.test(MultipleCacheManagersTest.java:979) > at org.infinispan.test.MultipleCacheManagersTest$TransactionalModeFilter.test(MultipleCacheManagersTest.java:966) > at org.infinispan.test.fwk.ChainMethodInterceptor.intercept(ChainMethodInterceptor.java:47) > at org.testng.TestRunner.intercept(TestRunner.java:795) > at org.testng.TestRunner.privateRun(TestRunner.java:741) > at org.testng.TestRunner.run(TestRunner.java:624) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:359) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312) > at org.testng.SuiteRunner.run(SuiteRunner.java:261) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1140) > at org.testng.TestNG.run(TestNG.java:1048) > at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72) > at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:123) > {code} > Trying to run it individually from command line results in: > {code} > [INFO] Running org.infinispan.functional.FunctionalMapTest > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.712 s - in org.infinispan.functional.FunctionalMapTest > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9385) Allow configuring near cache from hot rod properties

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9385?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9385. ------------------------------- > Allow configuring near cache from hot rod properties > ---------------------------------------------------- > > Key: ISPN-9385 > URL: https://issues.jboss.org/browse/ISPN-9385 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Hot Rod > Affects Versions: 9.4.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.0.CR1, 9.4.0.CR3 > > > The Hot Rod client should allow enabling near cache mode, max entries from the properties. It should also be possible to use regex patterns to match caches for which near cache will be enabled (default to all) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9628) infinispan-commons MANIFEST doesn not include Multi-Release entry

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9628?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9628: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6345, https://github.com/infinispan/infinispan/pull/6346 (was: https://github.com/infinispan/infinispan/pull/6345) > infinispan-commons MANIFEST doesn not include Multi-Release entry > ----------------------------------------------------------------- > > Key: ISPN-9628 > URL: https://issues.jboss.org/browse/ISPN-9628 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.4.0.Final, 9.3.3.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.4.1.Final, 9.3.4.Final > > > The Multi-Release:true entry is present in infinispan-commons test-jar but not in the main jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9628) infinispan-commons MANIFEST doesn not include Multi-Release entry

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9628?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9628: ---------------------------------- Status: Open (was: New) > infinispan-commons MANIFEST doesn not include Multi-Release entry > ----------------------------------------------------------------- > > Key: ISPN-9628 > URL: https://issues.jboss.org/browse/ISPN-9628 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.4.0.Final, 9.3.3.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.4.1.Final, 9.3.4.Final > > > The Multi-Release:true entry is present in infinispan-commons test-jar but not in the main jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9628) infinispan-commons MANIFEST doesn not include Multi-Release entry

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9628?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9628: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6345 > infinispan-commons MANIFEST doesn not include Multi-Release entry > ----------------------------------------------------------------- > > Key: ISPN-9628 > URL: https://issues.jboss.org/browse/ISPN-9628 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.4.0.Final, 9.3.3.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.4.1.Final, 9.3.4.Final > > > The Multi-Release:true entry is present in infinispan-commons test-jar but not in the main jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2018