April 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10104) Surefire maven plugin is not reporting properly the test name in the console

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10104?page=com.atlassian.jira.plugin... ] Diego Lovison updated ISPN-10104: --------------------------------- Summary: Surefire maven plugin is not reporting properly the test name in the console (was: Surefire maven plugin is not reporting properly the test name) > Surefire maven plugin is not reporting properly the test name in the console > ---------------------------------------------------------------------------- > > Key: ISPN-10104 > URL: https://issues.jboss.org/browse/ISPN-10104 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final, 9.4.11.Final > Reporter: Diego Lovison > Priority: Major > > After ISPN-9373 - Upgrade testng to 6.14.3 the surefire plugin started reporting the wrong test name > {noformat} > 16:12:52.388 [ERROR] Failures: > 16:12:52.388 [ERROR] org.infinispan.eviction.impl.ExceptionEvictionTest.eviction.ExceptionEvictionTest(org.infinispan.eviction.impl.ExceptionEvictionTest) > {noformat} > To reproduce add assert false in ExceptionEvictionTest.clearContent -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10104) Surefire maven plugin is not reporting properly the test name

by Diego Lovison (Jira)

Diego Lovison created ISPN-10104: ------------------------------------ Summary: Surefire maven plugin is not reporting properly the test name Key: ISPN-10104 URL: https://issues.jboss.org/browse/ISPN-10104 Project: Infinispan Issue Type: Bug Affects Versions: 9.4.11.Final, 10.0.0.Final Reporter: Diego Lovison After ISPN-9373 - Upgrade testng to 6.14.3 the surefire plugin started reporting the wrong test name {noformat} 16:12:52.388 [ERROR] Failures: 16:12:52.388 [ERROR] org.infinispan.eviction.impl.ExceptionEvictionTest.eviction.ExceptionEvictionTest(org.infinispan.eviction.impl.ExceptionEvictionTest) {noformat} To reproduce add assert false in ExceptionEvictionTest.clearContent -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10102) Off heap memory get/put byte should check for 1 byte, not 4

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10102?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10102: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6825 > Off heap memory get/put byte should check for 1 byte, not 4 > ----------------------------------------------------------- > > Key: ISPN-10102 > URL: https://issues.jboss.org/browse/ISPN-10102 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Affects Versions: 10.0.0.Beta3, 9.4.11.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > Off-heap's getByte/putByte code check that 4 bytes can be read/written when in reality it should only need 1 byte. > This will only show up if the byte is read/written at the end of a stream. I don't think it happens right now in the code but could happen in the future. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10102) Off heap memory get/put byte should check for 1 byte, not 4

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10102?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10102: ------------------------------------ Status: Open (was: New) > Off heap memory get/put byte should check for 1 byte, not 4 > ----------------------------------------------------------- > > Key: ISPN-10102 > URL: https://issues.jboss.org/browse/ISPN-10102 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Affects Versions: 10.0.0.Beta3, 9.4.11.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > Off-heap's getByte/putByte code check that 4 bytes can be read/written when in reality it should only need 1 byte. > This will only show up if the byte is read/written at the end of a stream. I don't think it happens right now in the code but could happen in the future. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10102) Off heap memory get/put byte should check for 1 byte, not 4

by Galder Zamarreño (Jira)

Galder Zamarreño created ISPN-10102: --------------------------------------- Summary: Off heap memory get/put byte should check for 1 byte, not 4 Key: ISPN-10102 URL: https://issues.jboss.org/browse/ISPN-10102 Project: Infinispan Issue Type: Bug Components: Off Heap Affects Versions: 9.4.11.Final, 10.0.0.Beta3 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 10.0.0.Beta4, 10.0.0.Final Off-heap's getByte/putByte code check that 4 bytes can be read/written when in reality it should only need 1 byte. This will only show up if the byte is read/written at the end of a stream. I don't think it happens right now in the code but could happen in the future. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-91) Allow SerializationContextInitializer dependencies

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-91?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-91: -------------------------------- Status: Open (was: New) > Allow SerializationContextInitializer dependencies > -------------------------------------------------- > > Key: IPROTO-91 > URL: https://issues.jboss.org/browse/IPROTO-91 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Nistor Adrian > Priority: Major > > In order to avoid split-packages across multiple maven modules and the resulting jars, it's necessary for Protostream to provide a mechanism for {{SerializationContextInitializer}} implementations in one module to depend on those defined in dependent modules. > For example, the {{org.infinispan.commons.io.ByteBufferImpl}} class is defined in the Infinispan commons module, but is required by several annotated Pojos in the core module. In order for the core module to compile, it is necessary for {{ByteBufferImpl.class}} to be added to the {{classes}} field in the core modules {{AutoProtoSchemaBuilder}} annotation with {{autoImportClasses == false}} or for {{autoImportClasses == true}}. Either way, this results in {{org.infinispan.commons.io.ByteBufferImp$_Marshaller.class}} being added to the core jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-91) Allow SerializationContextInitializer dependencies

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-91?page=com.atlassian.jira.plugin.... ] Work on IPROTO-91 started by Nistor Adrian. ------------------------------------------- > Allow SerializationContextInitializer dependencies > -------------------------------------------------- > > Key: IPROTO-91 > URL: https://issues.jboss.org/browse/IPROTO-91 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Nistor Adrian > Priority: Major > > In order to avoid split-packages across multiple maven modules and the resulting jars, it's necessary for Protostream to provide a mechanism for {{SerializationContextInitializer}} implementations in one module to depend on those defined in dependent modules. > For example, the {{org.infinispan.commons.io.ByteBufferImpl}} class is defined in the Infinispan commons module, but is required by several annotated Pojos in the core module. In order for the core module to compile, it is necessary for {{ByteBufferImpl.class}} to be added to the {{classes}} field in the core modules {{AutoProtoSchemaBuilder}} annotation with {{autoImportClasses == false}} or for {{autoImportClasses == true}}. Either way, this results in {{org.infinispan.commons.io.ByteBufferImp$_Marshaller.class}} being added to the core jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8835) Restructure query modules to allow non-indexed query with dependency only on core, query-dsl, object-filter modules

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8835?page=com.atlassian.jira.plugin.... ] Work on ISPN-8835 started by Nistor Adrian. ------------------------------------------- > Restructure query modules to allow non-indexed query with dependency only on core, query-dsl, object-filter modules > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8835 > URL: https://issues.jboss.org/browse/ISPN-8835 > Project: Infinispan > Issue Type: Feature Request > Environment: query module should only be needed when doing indexed query. > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8835) Restructure query modules to allow non-indexed query with dependency only on core, query-dsl, object-filter modules

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8835?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated ISPN-8835: -------------------------------- Status: Open (was: New) > Restructure query modules to allow non-indexed query with dependency only on core, query-dsl, object-filter modules > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8835 > URL: https://issues.jboss.org/browse/ISPN-8835 > Project: Infinispan > Issue Type: Feature Request > Environment: query module should only be needed when doing indexed query. > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10100) Some modules disable execution default-test but not java8-test

by Diego Lovison (Jira)

Diego Lovison created ISPN-10100: ------------------------------------ Summary: Some modules disable execution default-test but not java8-test Key: ISPN-10100 URL: https://issues.jboss.org/browse/ISPN-10100 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Affects Versions: 10.0.0.Beta3, 9.4.11.Final Reporter: Diego Lovison Assignee: Dan Berindei Fix For: 10.0.0.Beta4, 9.4.12.Final ISPN-9959 introduced executions {{java8-test}} and {{java10-test}}, but some modules (e.g. {{jcache/tck-runner}}) only disable the {{default-test}} execution when they want to skip Surefire completely. When profile {{java8-test}} is activated, Surefire tries to run the tests for those modules and fails: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (java8-test) on project infinispan-jcache-tck-runner: Illegal parallel='tests' -> [Help 1] {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2019