May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9193) CollectionMapper forEach should delegate to actualCollection

by William Burns (JIRA)

William Burns created ISPN-9193: ----------------------------------- Summary: CollectionMapper forEach should delegate to actualCollection Key: ISPN-9193 URL: https://issues.jboss.org/browse/ISPN-9193 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.Final Reporter: William Burns Assignee: William Burns Fix For: 9.3.0.CR1 CollectionMapper currently delegates forEach method to the stream instead of the underlying collection. This can cause issues since stream serializes the function across to be executed on all nodes. This should instead delegate to the actualCollection to allow for local operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9192) Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9192?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9192: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5999 > Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2 > ------------------------------------------------------------ > > Key: ISPN-9192 > URL: https://issues.jboss.org/browse/ISPN-9192 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build, Embedded Querying, Integration , Lucene Directory, WildFly modules > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.3.0.CR1 > > > We can upgrade to Hibernate Search {{5.10.0.Final}} to benefit the Infinispan Query component. > However, this is much easier if combined with the upgrade to Hibernate ORM {{5.3.0.Final}} as integration tests would not need to diverge (*JPA 2.2*). > Both these versions are included in WildFly 13. WildFly {{13.0.0.Beta1}} is available now so switching to this version to run integration test of the _Lucene Directory Modules_ already makes sense - as Infinispan no longer ships a dependency to a specific WildFly version: this is used only for integration tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9192) Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9192?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9192: ---------------------------------- Status: Open (was: New) > Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2 > ------------------------------------------------------------ > > Key: ISPN-9192 > URL: https://issues.jboss.org/browse/ISPN-9192 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build, Embedded Querying, Integration , Lucene Directory, WildFly modules > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.3.0.CR1 > > > We can upgrade to Hibernate Search {{5.10.0.Final}} to benefit the Infinispan Query component. > However, this is much easier if combined with the upgrade to Hibernate ORM {{5.3.0.Final}} as integration tests would not need to diverge (*JPA 2.2*). > Both these versions are included in WildFly 13. WildFly {{13.0.0.Beta1}} is available now so switching to this version to run integration test of the _Lucene Directory Modules_ already makes sense - as Infinispan no longer ships a dependency to a specific WildFly version: this is used only for integration tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9192) Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-9192: ------------------------------------- Summary: Upgrade to Hibernate Search 5.10, Hibernate ORM 5.3, JPA 2.2 Key: ISPN-9192 URL: https://issues.jboss.org/browse/ISPN-9192 Project: Infinispan Issue Type: Component Upgrade Components: Build, Embedded Querying, Integration , Lucene Directory, WildFly modules Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 9.3.0.CR1 We can upgrade to Hibernate Search {{5.10.0.Final}} to benefit the Infinispan Query component. However, this is much easier if combined with the upgrade to Hibernate ORM {{5.3.0.Final}} as integration tests would not need to diverge (*JPA 2.2*). Both these versions are included in WildFly 13. WildFly {{13.0.0.Beta1}} is available now so switching to this version to run integration test of the _Lucene Directory Modules_ already makes sense - as Infinispan no longer ships a dependency to a specific WildFly version: this is used only for integration tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7085) Add Codemirror editor for editing scripts

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7085?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7085: -------------------------------------- Status: Open (was: New) > Add Codemirror editor for editing scripts > ----------------------------------------- > > Key: ISPN-7085 > URL: https://issues.jboss.org/browse/ISPN-7085 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Vladimir Blagojevic > Priority: Minor > > We can utilise [CodeMirror|https://codemirror.net/] in our modals/text areas that require the creation of scripts in order to provide syntax highlighting, code completion etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9191) ExceptionEvictionTest random failure during clearContent

by William Burns (JIRA)

William Burns created ISPN-9191: ----------------------------------- Summary: ExceptionEvictionTest random failure during clearContent Key: ISPN-9191 URL: https://issues.jboss.org/browse/ISPN-9191 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: William Burns Assignee: William Burns Fix For: 9.3.0.CR1 There is a random failure that occurs for ExceptionEvictionTest. After each test is run we verify that there are no pending transactions leftover. It seems that the cause is due to the tx completion is sent asynchronously that we need to wait for them to clean up to verify. This is related to https://issues.jboss.org/browse/ISPN-9189 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9189) ExceptionEvictionTest test failure causes testng to panic

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9189?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9189: ------------------------------------ Caused by my ISPN-8554 changes, I didn't realize the `IConfigurationListener2.beforeConfiguration()` method isn't called when a configuration method is skipped. > ExceptionEvictionTest test failure causes testng to panic > --------------------------------------------------------- > > Key: ISPN-9189 > URL: https://issues.jboss.org/browse/ISPN-9189 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > > A single test failure is apparently causing 300+ cascade failures due to cleanup issues on testng. The first logged failure is: > {noformat} > ERROR] clearContent(org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.022 s <<< FAILURE! > java.lang.AssertionError: expected:<0> but was:<1> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) > at org.infinispan.eviction.impl.ExceptionEvictionTest.clearContent(ExceptionEvictionTest.java:197) > {noformat} > Followed by 300+ occcurences of: > {noformat} > [ERROR] testExceptionOnInsert[REPL_SYNC, nodeCount=3, storageType=OBJECT, optimisticTransaction=false](org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.001 s <<< FAILURE! > java.lang.NullPointerException > at org.infinispan.commons.test.RunningTestsRegistry.unregisterThreadWithTest(RunningTestsRegistry.java:39) > at org.infinispan.commons.test.TestNGTestListener.onConfigurationFailure(TestNGTestListener.java:142) > at org.testng.internal.Invoker.runConfigurationListeners(Invoker.java:1659) > at org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:299) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:237) > {noformat} > The related build is https://ci.infinispan.org/job/Infinispan/job/master/625/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9189) ExceptionEvictionTest test failure causes testng to panic

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9189?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9189: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5998 > ExceptionEvictionTest test failure causes testng to panic > --------------------------------------------------------- > > Key: ISPN-9189 > URL: https://issues.jboss.org/browse/ISPN-9189 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > > A single test failure is apparently causing 300+ cascade failures due to cleanup issues on testng. The first logged failure is: > {noformat} > ERROR] clearContent(org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.022 s <<< FAILURE! > java.lang.AssertionError: expected:<0> but was:<1> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) > at org.infinispan.eviction.impl.ExceptionEvictionTest.clearContent(ExceptionEvictionTest.java:197) > {noformat} > Followed by 300+ occcurences of: > {noformat} > [ERROR] testExceptionOnInsert[REPL_SYNC, nodeCount=3, storageType=OBJECT, optimisticTransaction=false](org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.001 s <<< FAILURE! > java.lang.NullPointerException > at org.infinispan.commons.test.RunningTestsRegistry.unregisterThreadWithTest(RunningTestsRegistry.java:39) > at org.infinispan.commons.test.TestNGTestListener.onConfigurationFailure(TestNGTestListener.java:142) > at org.testng.internal.Invoker.runConfigurationListeners(Invoker.java:1659) > at org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:299) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:237) > {noformat} > The related build is https://ci.infinispan.org/job/Infinispan/job/master/625/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9190) Make trace logging faster by writing a separate log file for each test

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9190: ---------------------------------- Summary: Make trace logging faster by writing a separate log file for each test Key: ISPN-9190 URL: https://issues.jboss.org/browse/ISPN-9190 Project: Infinispan Issue Type: Enhancement Components: Build Affects Versions: 9.3.0.Beta1 Reporter: Dan Berindei Priority: Minor Fix For: 9.3.0.CR1 Logging each test to a separate file is cheaper because each test uses a separate appender, so there's no contention. The total size may also be smaller (with {{CompressedFileAppender}}) because the test name is repeated a lot and there isn't so much overlap between different tests. Most important, keeping only the logs of failed tests becomes much faster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9190) Make trace logging faster by writing a separate log file for each test

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9190?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9190: ------------------------------- Status: Open (was: New) > Make trace logging faster by writing a separate log file for each test > ---------------------------------------------------------------------- > > Key: ISPN-9190 > URL: https://issues.jboss.org/browse/ISPN-9190 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.3.0.CR1 > > > Logging each test to a separate file is cheaper because each test uses a separate appender, so there's no contention. The total size may also be smaller (with {{CompressedFileAppender}}) because the test name is repeated a lot and there isn't so much overlap between different tests. > Most important, keeping only the logs of failed tests becomes much faster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 May 2018