December 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8631) GetAllCacheNotFoundResponseTest.createBeforeClass fails

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8631?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8631: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5642 > GetAllCacheNotFoundResponseTest.createBeforeClass fails > ------------------------------------------------------- > > Key: ISPN-8631 > URL: https://issues.jboss.org/browse/ISPN-8631 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.2.0.Beta2 > > > With a controlled CHF, a segment can have fewer than {{numOwners}} owners while the cluster is smaller than expected. That means {{MultipleCacheManagersTest.createClusteredCaches()}} should call {{waitForClusterToForm()}} only after starting all the nodes, not in each iteration, or it will time out waiting for all segments to have {{numOwners}} owners. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8631) GetAllCacheNotFoundResponseTest.createBeforeClass fails

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8631: ---------------------------------- Summary: GetAllCacheNotFoundResponseTest.createBeforeClass fails Key: ISPN-8631 URL: https://issues.jboss.org/browse/ISPN-8631 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.2.0.Beta2 With a controlled CHF, a segment can have fewer than {{numOwners}} owners while the cluster is smaller than expected. That means {{MultipleCacheManagersTest.createClusteredCaches()}} should call {{waitForClusterToForm()}} only after starting all the nodes, not in each iteration, or it will time out waiting for all segments to have {{numOwners}} owners. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8563) Caching Service / Shared Memory Getting Started guide

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8563?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-8563: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-container-images/jboss-dataservices-image/pull/46 > Caching Service / Shared Memory Getting Started guide > ----------------------------------------------------- > > Key: ISPN-8563 > URL: https://issues.jboss.org/browse/ISPN-8563 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud, Documentation-Servers > Reporter: Tristan Tarrant > Assignee: John Brier > > We need a getting started guide that lives with the images code and that can be published to the KB -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8563) Caching Service / Shared Memory Getting Started guide

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8563?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-8563: ------------------------------- Status: Open (was: New) > Caching Service / Shared Memory Getting Started guide > ----------------------------------------------------- > > Key: ISPN-8563 > URL: https://issues.jboss.org/browse/ISPN-8563 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud, Documentation-Servers > Reporter: Tristan Tarrant > Assignee: John Brier > > We need a getting started guide that lives with the images code and that can be published to the KB -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8630) Integration tests should start server in the pre-integration-test phase

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8630?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8630: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5641 > Integration tests should start server in the pre-integration-test phase > ----------------------------------------------------------------------- > > Key: ISPN-8630 > URL: https://issues.jboss.org/browse/ISPN-8630 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Beta2 > > > Some profiles in {{infinispan-server-testsuite}} require an external server, started with {{maven-antrun-plugin}} in the {{generate-test-resources}} phase. As the server might require resources modified in the {{process-test-resources}} phase, it's best to start the server in the {{pre-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8630) Integration tests should start server in the pre-integration-test phase

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8630?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8630: ------------------------------- Status: Open (was: New) > Integration tests should start server in the pre-integration-test phase > ----------------------------------------------------------------------- > > Key: ISPN-8630 > URL: https://issues.jboss.org/browse/ISPN-8630 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Beta2 > > > Some profiles in {{infinispan-server-testsuite}} require an external server, started with {{maven-antrun-plugin}} in the {{generate-test-resources}} phase. As the server might require resources modified in the {{process-test-resources}} phase, it's best to start the server in the {{pre-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8630) Integration tests should start server in the pre-integration-test phase

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8630: ---------------------------------- Summary: Integration tests should start server in the pre-integration-test phase Key: ISPN-8630 URL: https://issues.jboss.org/browse/ISPN-8630 Project: Infinispan Issue Type: Task Components: Test Suite - Server Affects Versions: 9.2.0.Beta1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.2.0.Beta2 Some profiles in {{infinispan-server-testsuite}} require an external server, started with {{maven-antrun-plugin}} in the {{generate-test-resources}} phase. As the server might require resources modified in the {{process-test-resources}} phase, it's best to start the server in the {{pre-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8629) Javadoc modules' build invokes a new instance of Maven

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8629?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8629: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5640 Configuring maven-javadoc-plugin with detectOfflineLinks=false eliminates the Maven invocations. > Javadoc modules' build invokes a new instance of Maven > ------------------------------------------------------ > > Key: ISPN-8629 > URL: https://issues.jboss.org/browse/ISPN-8629 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.2.0.Beta1, 9.1.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Beta2 > > > During the javadoc modules build, {{maven-javadoc-plugin}} tries to detect the apidocs location of each dependency. If a module dependency doesn't have an apidocs directory, it tries to run a new Maven instance in order to build it, leading to messages like this: > {noformat} > [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc' has not been previously called for the module: 'org.infinispan:infinispan-extended-statistics:jar:9.2.0-SNAPSHOT'. Trying to invoke it... > [ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file: /home/dan/Work/infinispan/javadoc/javadoc-embedded/target/invoker/maven-javadoc-plugin2134174433.txt > [WARNING] Creating fake javadoc directory to prevent repeated invocations: /home/dan/Work/infinispan/extended-statistics/target/apidocs > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8629) Javadoc modules' build invokes a new instance of Maven

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8629: ---------------------------------- Summary: Javadoc modules' build invokes a new instance of Maven Key: ISPN-8629 URL: https://issues.jboss.org/browse/ISPN-8629 Project: Infinispan Issue Type: Bug Components: Build Affects Versions: 9.1.3.Final, 9.2.0.Beta1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.2.0.Beta2 During the javadoc modules build, {{maven-javadoc-plugin}} tries to detect the apidocs location of each dependency. If a module dependency doesn't have an apidocs directory, it tries to run a new Maven instance in order to build it, leading to messages like this: {noformat} [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc' has not been previously called for the module: 'org.infinispan:infinispan-extended-statistics:jar:9.2.0-SNAPSHOT'. Trying to invoke it... [ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file: /home/dan/Work/infinispan/javadoc/javadoc-embedded/target/invoker/maven-javadoc-plugin2134174433.txt [WARNING] Creating fake javadoc directory to prevent repeated invocations: /home/dan/Work/infinispan/extended-statistics/target/apidocs {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8629) Javadoc modules' build invokes a new instance of Maven

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8629?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8629: ------------------------------- Status: Open (was: New) > Javadoc modules' build invokes a new instance of Maven > ------------------------------------------------------ > > Key: ISPN-8629 > URL: https://issues.jboss.org/browse/ISPN-8629 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.2.0.Beta1, 9.1.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Beta2 > > > During the javadoc modules build, {{maven-javadoc-plugin}} tries to detect the apidocs location of each dependency. If a module dependency doesn't have an apidocs directory, it tries to run a new Maven instance in order to build it, leading to messages like this: > {noformat} > [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc' has not been previously called for the module: 'org.infinispan:infinispan-extended-statistics:jar:9.2.0-SNAPSHOT'. Trying to invoke it... > [ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file: /home/dan/Work/infinispan/javadoc/javadoc-embedded/target/invoker/maven-javadoc-plugin2134174433.txt > [WARNING] Creating fake javadoc directory to prevent repeated invocations: /home/dan/Work/infinispan/extended-statistics/target/apidocs > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2017