[jira] [Updated] (GEODE-10220) Coredump while initializing PdxType remoteToLocal
[ https://issues.apache.org/jira/browse/GEODE-10220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10220: -- Labels: needsTriage (was: ) > Coredump while initializing PdxType remoteToLocal > - > > Key: GEODE-10220 > URL: https://issues.apache.org/jira/browse/GEODE-10220 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Priority: Major > Labels: needsTriage > > *GIVEN* a cluster with 1 server and 1 locator > *AND* a native client connected to the cluster > *WHEN* deserializing a PdxSerializable like object > *AND* and a new PdxType is fetched from the server > *THEN* a coredump happens whenever initializing the remoteToLocal map. > --- > *Additional information.* The coredump happens whenever > PdxType::initRemoteToLocal is called -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10220) Coredump while initializing PdxType remoteToLocal
Mario Salazar de Torres created GEODE-10220: --- Summary: Coredump while initializing PdxType remoteToLocal Key: GEODE-10220 URL: https://issues.apache.org/jira/browse/GEODE-10220 Project: Geode Issue Type: Bug Components: native client Reporter: Mario Salazar de Torres *GIVEN* a cluster with 1 server and 1 locator *AND* a native client connected to the cluster *WHEN* deserializing a PdxSerializable like object *AND* and a new PdxType is fetched from the server *THEN* a coredump happens whenever initializing the remoteToLocal map. --- *Additional information.* The coredump happens whenever PdxType::initRemoteToLocal is called -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10220) Coredump while initializing PdxType remoteToLocal
[ https://issues.apache.org/jira/browse/GEODE-10220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Salazar de Torres reassigned GEODE-10220: --- Assignee: Mario Salazar de Torres > Coredump while initializing PdxType remoteToLocal > - > > Key: GEODE-10220 > URL: https://issues.apache.org/jira/browse/GEODE-10220 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: needsTriage > > *GIVEN* a cluster with 1 server and 1 locator > *AND* a native client connected to the cluster > *WHEN* deserializing a PdxSerializable like object > *AND* and a new PdxType is fetched from the server > *THEN* a coredump happens whenever initializing the remoteToLocal map. > --- > *Additional information.* The coredump happens whenever > PdxType::initRemoteToLocal is called -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10204) Add unit test cases for SizeableByteArrayList
[
https://issues.apache.org/jira/browse/GEODE-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10204:
---
Labels: pull-request-available (was: )
> Add unit test cases for SizeableByteArrayList
> -
>
> Key: GEODE-10204
> URL: https://issues.apache.org/jira/browse/GEODE-10204
> Project: Geode
> Issue Type: Test
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: Bala Tripura Sundari Kaza Venkata
>Priority: Major
> Labels: pull-request-available
>
> For example, {{clearSublist()}} was added for LTRIM support and needs unit
> tests. Any public method that does not just call the {{super()}} method on
> {{LinkedList}} should have coverage.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10204) Add unit test cases for SizeableByteArrayList
[
https://issues.apache.org/jira/browse/GEODE-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bala Tripura Sundari Kaza Venkata reassigned GEODE-10204:
-
Assignee: Bala Tripura Sundari Kaza Venkata
> Add unit test cases for SizeableByteArrayList
> -
>
> Key: GEODE-10204
> URL: https://issues.apache.org/jira/browse/GEODE-10204
> Project: Geode
> Issue Type: Test
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: Bala Tripura Sundari Kaza Venkata
>Priority: Major
>
> For example, {{clearSublist()}} was added for LTRIM support and needs unit
> tests. Any public method that does not just call the {{super()}} method on
> {{LinkedList}} should have coverage.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Reopened] (GEODE-10127) Incorrect locator hostname used in remote locator connections
[
https://issues.apache.org/jira/browse/GEODE-10127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett reopened GEODE-10127:
---
> Incorrect locator hostname used in remote locator connections
> -
>
> Key: GEODE-10127
> URL: https://issues.apache.org/jira/browse/GEODE-10127
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available
> Fix For: 1.15.0
>
>
> When locators in distributed system (DS) B as for locators in DS A they are
> sent the local host name and IP address of the locators and not that of the
> {{hostname-for-clients}} or {{bind-address}} properties.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10221) RedisList does not set memory usage correctly when creating a copy
[
https://issues.apache.org/jira/browse/GEODE-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-10221:
--
Assignee: Jens Deppe
> RedisList does not set memory usage correctly when creating a copy
> --
>
> Key: GEODE-10221
> URL: https://issues.apache.org/jira/browse/GEODE-10221
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> Since adding a constructor to {{RedisList}} that takes another list in order
> to create a copy, we don't update the memory overhead of the new list
> correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10221) RedisList does not set memory usage correctly when creating a copy
Jens Deppe created GEODE-10221:
--
Summary: RedisList does not set memory usage correctly when
creating a copy
Key: GEODE-10221
URL: https://issues.apache.org/jira/browse/GEODE-10221
Project: Geode
Issue Type: Improvement
Components: redis
Reporter: Jens Deppe
Since adding a constructor to {{RedisList}} that takes another list in order to
create a copy, we don't update the memory overhead of the new list correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10203) GetClusterConfigurationFunction should have a UUID
[ https://issues.apache.org/jira/browse/GEODE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519002#comment-17519002 ] ASF subversion and git services commented on GEODE-10203: - Commit 5a698f55e0755381ac3eb0ed06fc10e98826d89a in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5a698f55e0 ] GEODE-10203: SerialVersionUID added. (#7529) * SerialVersionUID added to GetClusterConfigurationFunction. * Changes to this class will prevent breaking backward compatibility. > GetClusterConfigurationFunction should have a UUID > -- > > Key: GEODE-10203 > URL: https://issues.apache.org/jira/browse/GEODE-10203 > Project: Geode > Issue Type: Bug > Components: serialization >Affects Versions: 1.15.0 >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > GetClusterConfigurationFunction needs to have a serialVersionUUID so that any > future changes in the class do not change the versionID and does not break > the backwards compartibiliity -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10203) GetClusterConfigurationFunction should have a UUID
[ https://issues.apache.org/jira/browse/GEODE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag resolved GEODE-10203. - Resolution: Fixed > GetClusterConfigurationFunction should have a UUID > -- > > Key: GEODE-10203 > URL: https://issues.apache.org/jira/browse/GEODE-10203 > Project: Geode > Issue Type: Bug > Components: serialization >Affects Versions: 1.15.0 >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > GetClusterConfigurationFunction needs to have a serialVersionUUID so that any > future changes in the class do not change the versionID and does not break > the backwards compartibiliity -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10221) RedisList does not set memory usage correctly when creating a copy
[
https://issues.apache.org/jira/browse/GEODE-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10221:
---
Labels: pull-request-available (was: )
> RedisList does not set memory usage correctly when creating a copy
> --
>
> Key: GEODE-10221
> URL: https://issues.apache.org/jira/browse/GEODE-10221
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> Since adding a constructor to {{RedisList}} that takes another list in order
> to create a copy, we don't update the memory overhead of the new list
> correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9980) Startup of Locator or Server should fail fast if geode.enableGlobalSerialFilter is enabled but fails configuration
[
https://issues.apache.org/jira/browse/GEODE-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519034#comment-17519034
]
ASF subversion and git services commented on GEODE-9980:
Commit dc042f5f62453eea5e80e9407bee04bf861d568b in geode's branch
refs/heads/support/1.12 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc042f5f62 ]
[1.12] GEODE-9980: Revert serialization filter changes from 1.12 (#7563)
* Revert "GEODE-9980: Improve error handling of serial filters (#7299)"
This reverts commit 75fa13675c320a465245a78f7a841d0016860fc9.
* Revert "GEODE-9758: Add internal serial filter API (#7217)"
This reverts commit 03fe0cb9734046a1c018501306c694e642f8ccdd.
* Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)"
This reverts commit b69ee52ee3e80b6a7d5ee8e22012c531eef65534.
* Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)"
This reverts commit a9d5f0cf49d3986e5c27bdd9460b939305499e0c.
* Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)"
This reverts commit 40037b4de64333452547cb203b0b6793c59d3f8f.
* Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule
(#7121)"
This reverts commit e55fedbc478759052e13b6e3b837e1667b39d00f.
> Startup of Locator or Server should fail fast if
> geode.enableGlobalSerialFilter is enabled but fails configuration
> --
>
> Key: GEODE-9980
> URL: https://issues.apache.org/jira/browse/GEODE-9980
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> The following error conditions need better handling which includes handling
> of all errors consistently and cause the startup of a Locator or Server to
> fail if it's unable to honor the setting of
> {{-Dgeode.enableGlobalSerialFilter=true}} for any reason. Currently, if
> {{-Dgeode.enableGlobalSerialFilter=true}} is specified but Geode is unable to
> create a global serial filter, then it will will log a warning and continue
> running. A user may easily miss that log statement and believe that the JVM
> is running with a properly configured serialization filter.
> 1) The user is trying to secure the JVM very thoroughly and accidentally
> specifies both {{-Djdk.serialFilter}} and
> {{-Dgeode.enableGlobalSerialFilter}}.
> 2) The user runs some non-Geode code in the same JVM that invokes
> {{ObjectInputFilter.Config.setFilter(...)}} directly.
> 3) The user is using a version of Java 8 prior to 8u121 (the release that
> first added {{sun.misc.ObjectInputFilter}}) and specifies
> {{-Dgeode.enableGlobalSerialFilter=true}}. Also, the same behavior occurs if
> they do NOT specify enabling that property.
> 4) {{LocatorLauncher}} or {{ServerLauncher}} is started in a JVM that has
> already created at least one {{ObjectInputStream}} which will cause
> {{ObjectInputFilter.Config.setFilter(...)}} to fail.
> 5) {{LocatorLauncher}} or {{ServerLauncher}} is started in a Java 8 JVM that
> is not based on OpenJDK (ie {{sun.misc.ObjectInputFilter}} does not exist).
> 6) {{LocatorLauncher}} or {{ServerLauncher}} is started in an unforeseen
> environment that causes invocation of
> {{ObjectInputFilter.Config.setFilter(...)}} via Java Reflection to throw
> {{IllegalAccessException}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9879) Extract part of SystemPropertyHelper to geode-common for wider use
[ https://issues.apache.org/jira/browse/GEODE-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519036#comment-17519036 ] ASF subversion and git services commented on GEODE-9879: Commit dc042f5f62453eea5e80e9407bee04bf861d568b in geode's branch refs/heads/support/1.12 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc042f5f62 ] [1.12] GEODE-9980: Revert serialization filter changes from 1.12 (#7563) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 75fa13675c320a465245a78f7a841d0016860fc9. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 03fe0cb9734046a1c018501306c694e642f8ccdd. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit b69ee52ee3e80b6a7d5ee8e22012c531eef65534. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit a9d5f0cf49d3986e5c27bdd9460b939305499e0c. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 40037b4de64333452547cb203b0b6793c59d3f8f. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit e55fedbc478759052e13b6e3b837e1667b39d00f. > Extract part of SystemPropertyHelper to geode-common for wider use > -- > > Key: GEODE-9879 > URL: https://issues.apache.org/jira/browse/GEODE-9879 > Project: Geode > Issue Type: Wish > Components: core >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > I need to use the dual property prefix part of SystemPropertyHelper to > geode-common so that it can be used from non-core geode modules such as > geode-serialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9879) Extract part of SystemPropertyHelper to geode-common for wider use
[ https://issues.apache.org/jira/browse/GEODE-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519040#comment-17519040 ] ASF subversion and git services commented on GEODE-9879: Commit 01a101c3e479a50b9cca26b8c836e7ba10d1a60c in geode's branch refs/heads/support/1.13 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=01a101c3e4 ] [1.13] GEODE-9980: Revert serialization filter changes from 1.13 (#7562) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 240feb88cdfbc2db44bec28ff23b079dc07b0c41. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 220ea534973edbb2643df6476e349d783b04b21e. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 06bb3a66125e0c9f8c5dbe7ee579e44d462d802d. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit 31810b5bd6fdd09b60890b427af60a9542bac954. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 1c21af7561fc52ee771203c33d321124adbc4b25. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit 68e7d6e577ffc6c2b98d6611d05c6a6e98bd3358. > Extract part of SystemPropertyHelper to geode-common for wider use > -- > > Key: GEODE-9879 > URL: https://issues.apache.org/jira/browse/GEODE-9879 > Project: Geode > Issue Type: Wish > Components: core >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > I need to use the dual property prefix part of SystemPropertyHelper to > geode-common so that it can be used from non-core geode modules such as > geode-serialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9817) Allow analyze serializables tests to provide custom source set paths to ClassAnalysisRule
[ https://issues.apache.org/jira/browse/GEODE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519037#comment-17519037 ] ASF subversion and git services commented on GEODE-9817: Commit dc042f5f62453eea5e80e9407bee04bf861d568b in geode's branch refs/heads/support/1.12 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc042f5f62 ] [1.12] GEODE-9980: Revert serialization filter changes from 1.12 (#7563) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 75fa13675c320a465245a78f7a841d0016860fc9. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 03fe0cb9734046a1c018501306c694e642f8ccdd. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit b69ee52ee3e80b6a7d5ee8e22012c531eef65534. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit a9d5f0cf49d3986e5c27bdd9460b939305499e0c. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 40037b4de64333452547cb203b0b6793c59d3f8f. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit e55fedbc478759052e13b6e3b837e1667b39d00f. > Allow analyze serializables tests to provide custom source set paths to > ClassAnalysisRule > - > > Key: GEODE-9817 > URL: https://issues.apache.org/jira/browse/GEODE-9817 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > In order to make SanctionedSerializablesService and the related tests to be > more pluggable by external modules, I need to make changes to allow analyze > serializables tests to provide custom source set paths to ClassAnalysisRule. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9758) Provide an easy to configure a process-wide serialization filter for use on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519035#comment-17519035 ] ASF subversion and git services commented on GEODE-9758: Commit dc042f5f62453eea5e80e9407bee04bf861d568b in geode's branch refs/heads/support/1.12 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc042f5f62 ] [1.12] GEODE-9980: Revert serialization filter changes from 1.12 (#7563) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 75fa13675c320a465245a78f7a841d0016860fc9. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 03fe0cb9734046a1c018501306c694e642f8ccdd. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit b69ee52ee3e80b6a7d5ee8e22012c531eef65534. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit a9d5f0cf49d3986e5c27bdd9460b939305499e0c. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 40037b4de64333452547cb203b0b6793c59d3f8f. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit e55fedbc478759052e13b6e3b837e1667b39d00f. > Provide an easy to configure a process-wide serialization filter for use on > Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement > Components: configuration, serialization >Affects Versions: 1.12.7, 1.13.0, 1.14.0 >Reporter: Jianxia Chen >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, docs, pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > Provide an easy way to configure a process-wide serialization filter for use > on Java 8. When enabled, validate-serializable-objects should be enabled and > the process-wide serialization filter should be configured to accept only JDK > classes and Geode classes in addition to anything the user might specify with > serializable-object-filter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9980) Startup of Locator or Server should fail fast if geode.enableGlobalSerialFilter is enabled but fails configuration
[
https://issues.apache.org/jira/browse/GEODE-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519038#comment-17519038
]
ASF subversion and git services commented on GEODE-9980:
Commit 01a101c3e479a50b9cca26b8c836e7ba10d1a60c in geode's branch
refs/heads/support/1.13 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=01a101c3e4 ]
[1.13] GEODE-9980: Revert serialization filter changes from 1.13 (#7562)
* Revert "GEODE-9980: Improve error handling of serial filters (#7299)"
This reverts commit 240feb88cdfbc2db44bec28ff23b079dc07b0c41.
* Revert "GEODE-9758: Add internal serial filter API (#7217)"
This reverts commit 220ea534973edbb2643df6476e349d783b04b21e.
* Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)"
This reverts commit 06bb3a66125e0c9f8c5dbe7ee579e44d462d802d.
* Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)"
This reverts commit 31810b5bd6fdd09b60890b427af60a9542bac954.
* Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)"
This reverts commit 1c21af7561fc52ee771203c33d321124adbc4b25.
* Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule
(#7121)"
This reverts commit 68e7d6e577ffc6c2b98d6611d05c6a6e98bd3358.
> Startup of Locator or Server should fail fast if
> geode.enableGlobalSerialFilter is enabled but fails configuration
> --
>
> Key: GEODE-9980
> URL: https://issues.apache.org/jira/browse/GEODE-9980
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> The following error conditions need better handling which includes handling
> of all errors consistently and cause the startup of a Locator or Server to
> fail if it's unable to honor the setting of
> {{-Dgeode.enableGlobalSerialFilter=true}} for any reason. Currently, if
> {{-Dgeode.enableGlobalSerialFilter=true}} is specified but Geode is unable to
> create a global serial filter, then it will will log a warning and continue
> running. A user may easily miss that log statement and believe that the JVM
> is running with a properly configured serialization filter.
> 1) The user is trying to secure the JVM very thoroughly and accidentally
> specifies both {{-Djdk.serialFilter}} and
> {{-Dgeode.enableGlobalSerialFilter}}.
> 2) The user runs some non-Geode code in the same JVM that invokes
> {{ObjectInputFilter.Config.setFilter(...)}} directly.
> 3) The user is using a version of Java 8 prior to 8u121 (the release that
> first added {{sun.misc.ObjectInputFilter}}) and specifies
> {{-Dgeode.enableGlobalSerialFilter=true}}. Also, the same behavior occurs if
> they do NOT specify enabling that property.
> 4) {{LocatorLauncher}} or {{ServerLauncher}} is started in a JVM that has
> already created at least one {{ObjectInputStream}} which will cause
> {{ObjectInputFilter.Config.setFilter(...)}} to fail.
> 5) {{LocatorLauncher}} or {{ServerLauncher}} is started in a Java 8 JVM that
> is not based on OpenJDK (ie {{sun.misc.ObjectInputFilter}} does not exist).
> 6) {{LocatorLauncher}} or {{ServerLauncher}} is started in an unforeseen
> environment that causes invocation of
> {{ObjectInputFilter.Config.setFilter(...)}} via Java Reflection to throw
> {{IllegalAccessException}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9817) Allow analyze serializables tests to provide custom source set paths to ClassAnalysisRule
[ https://issues.apache.org/jira/browse/GEODE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519041#comment-17519041 ] ASF subversion and git services commented on GEODE-9817: Commit 01a101c3e479a50b9cca26b8c836e7ba10d1a60c in geode's branch refs/heads/support/1.13 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=01a101c3e4 ] [1.13] GEODE-9980: Revert serialization filter changes from 1.13 (#7562) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 240feb88cdfbc2db44bec28ff23b079dc07b0c41. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 220ea534973edbb2643df6476e349d783b04b21e. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 06bb3a66125e0c9f8c5dbe7ee579e44d462d802d. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit 31810b5bd6fdd09b60890b427af60a9542bac954. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 1c21af7561fc52ee771203c33d321124adbc4b25. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit 68e7d6e577ffc6c2b98d6611d05c6a6e98bd3358. > Allow analyze serializables tests to provide custom source set paths to > ClassAnalysisRule > - > > Key: GEODE-9817 > URL: https://issues.apache.org/jira/browse/GEODE-9817 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > In order to make SanctionedSerializablesService and the related tests to be > more pluggable by external modules, I need to make changes to allow analyze > serializables tests to provide custom source set paths to ClassAnalysisRule. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9758) Provide an easy to configure a process-wide serialization filter for use on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519039#comment-17519039 ] ASF subversion and git services commented on GEODE-9758: Commit 01a101c3e479a50b9cca26b8c836e7ba10d1a60c in geode's branch refs/heads/support/1.13 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=01a101c3e4 ] [1.13] GEODE-9980: Revert serialization filter changes from 1.13 (#7562) * Revert "GEODE-9980: Improve error handling of serial filters (#7299)" This reverts commit 240feb88cdfbc2db44bec28ff23b079dc07b0c41. * Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit 220ea534973edbb2643df6476e349d783b04b21e. * Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 06bb3a66125e0c9f8c5dbe7ee579e44d462d802d. * Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit 31810b5bd6fdd09b60890b427af60a9542bac954. * Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 1c21af7561fc52ee771203c33d321124adbc4b25. * Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7121)" This reverts commit 68e7d6e577ffc6c2b98d6611d05c6a6e98bd3358. > Provide an easy to configure a process-wide serialization filter for use on > Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement > Components: configuration, serialization >Affects Versions: 1.12.7, 1.13.0, 1.14.0 >Reporter: Jianxia Chen >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, docs, pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > Provide an easy way to configure a process-wide serialization filter for use > on Java 8. When enabled, validate-serializable-objects should be enabled and > the process-wide serialization filter should be configured to accept only JDK > classes and Geode classes in addition to anything the user might specify with > serializable-object-filter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10222) Null memberID in GII of persistent region with concurrent region destroy causes AssertionError
[
https://issues.apache.org/jira/browse/GEODE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10222:
--
Labels: needsTriage (was: )
> Null memberID in GII of persistent region with concurrent region destroy
> causes AssertionError
> --
>
> Key: GEODE-10222
> URL: https://issues.apache.org/jira/browse/GEODE-10222
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> The below stack trace was observed while concurrent region creates and
> destroys were being performed on a persistent replicated region:
> {noformat}
> java.lang.AssertionError: Member id should not be null for persistent version
> tags
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.versions.DiskVersionTag.replaceNullIDs(DiskVersionTag.java:47)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:975)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1312)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:214)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2858)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:197)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:190)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doHighPriorityThread(ClusterOperationExecutors.java:402)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at Remote Member 'localhost(server2:13075):41003' in
> java.lang.Thread.run(Thread.java:748)
> at
> org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:90)
> at
> org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:562)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1249)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986){noformat}
> The {{AssertionError}} thrown by {{DiskVersionTag.replaceNullIDs()}} is not
> handled by any of the calling methods, which leads to the GII failing without
> attempting to retry, and does not decrement the getInitialImagesInProgress
> stat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10222) Null memberID in GII of persistent region with concurrent region destroy causes AssertionError
Donal Evans created GEODE-10222:
---
Summary: Null memberID in GII of persistent region with concurrent
region destroy causes AssertionError
Key: GEODE-10222
URL: https://issues.apache.org/jira/browse/GEODE-10222
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Donal Evans
The below stack trace was observed while concurrent region creates and destroys
were being performed on a persistent replicated region:
{noformat}
java.lang.AssertionError: Member id should not be null for persistent version
tags
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.internal.cache.versions.DiskVersionTag.replaceNullIDs(DiskVersionTag.java:47)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:975)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1312)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:214)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2858)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:197)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:190)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
at Remote Member 'localhost(server2:13075):41003' in
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at Remote Member 'localhost(server2:13075):41003' in
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.distributed.internal.ClusterOperationExecutors.doHighPriorityThread(ClusterOperationExecutors.java:402)
at Remote Member 'localhost(server2:13075):41003' in
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
at Remote Member 'localhost(server2:13075):41003' in
java.lang.Thread.run(Thread.java:748)
at
org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:90)
at
org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:562)
at
org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1249)
at
org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
at
org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
at
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
at
org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986){noformat}
The {{AssertionError}} thrown by {{DiskVersionTag.replaceNullIDs()}} is not
handled by any of the calling methods, which leads to the GII failing without
attempting to retry, and does not decrement the getInitialImagesInProgress stat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10222) Null memberID in GII of persistent region with concurrent region destroy causes AssertionError
[
https://issues.apache.org/jira/browse/GEODE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans reassigned GEODE-10222:
---
Assignee: Donal Evans
> Null memberID in GII of persistent region with concurrent region destroy
> causes AssertionError
> --
>
> Key: GEODE-10222
> URL: https://issues.apache.org/jira/browse/GEODE-10222
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> The below stack trace was observed while concurrent region creates and
> destroys were being performed on a persistent replicated region:
> {noformat}
> java.lang.AssertionError: Member id should not be null for persistent version
> tags
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.versions.DiskVersionTag.replaceNullIDs(DiskVersionTag.java:47)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:975)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1312)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:214)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2858)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:197)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:190)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doHighPriorityThread(ClusterOperationExecutors.java:402)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at Remote Member 'localhost(server2:13075):41003' in
> java.lang.Thread.run(Thread.java:748)
> at
> org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:90)
> at
> org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:562)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1249)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986){noformat}
> The {{AssertionError}} thrown by {{DiskVersionTag.replaceNullIDs()}} is not
> handled by any of the calling methods, which leads to the GII failing without
> attempting to retry, and does not decrement the getInitialImagesInProgress
> stat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10222) Null memberID in GII of persistent region with concurrent region destroy causes AssertionError
[
https://issues.apache.org/jira/browse/GEODE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10222:
Labels: blocks-1.15.0 (was: needsTriage)
> Null memberID in GII of persistent region with concurrent region destroy
> causes AssertionError
> --
>
> Key: GEODE-10222
> URL: https://issues.apache.org/jira/browse/GEODE-10222
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: blocks-1.15.0
>
> The below stack trace was observed while concurrent region creates and
> destroys were being performed on a persistent replicated region:
> {noformat}
> java.lang.AssertionError: Member id should not be null for persistent version
> tags
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.versions.DiskVersionTag.replaceNullIDs(DiskVersionTag.java:47)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:975)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1312)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:214)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2858)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:197)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:190)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doHighPriorityThread(ClusterOperationExecutors.java:402)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at Remote Member 'localhost(server2:13075):41003' in
> java.lang.Thread.run(Thread.java:748)
> at
> org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:90)
> at
> org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:562)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1249)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986){noformat}
> The {{AssertionError}} thrown by {{DiskVersionTag.replaceNullIDs()}} is not
> handled by any of the calling methods, which leads to the GII failing without
> attempting to retry, and does not decrement the getInitialImagesInProgress
> stat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10222) Null memberID in GII of persistent region with concurrent region destroy causes AssertionError
[
https://issues.apache.org/jira/browse/GEODE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10222:
---
Labels: blocks-1.15.0 pull-request-available (was: blocks-1.15.0)
> Null memberID in GII of persistent region with concurrent region destroy
> causes AssertionError
> --
>
> Key: GEODE-10222
> URL: https://issues.apache.org/jira/browse/GEODE-10222
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available
>
> The below stack trace was observed while concurrent region creates and
> destroys were being performed on a persistent replicated region:
> {noformat}
> java.lang.AssertionError: Member id should not be null for persistent version
> tags
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.versions.DiskVersionTag.replaceNullIDs(DiskVersionTag.java:47)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:975)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1312)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:214)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2858)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:197)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:190)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at Remote Member 'localhost(server2:13075):41003' in
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doHighPriorityThread(ClusterOperationExecutors.java:402)
> at Remote Member 'localhost(server2:13075):41003' in
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at Remote Member 'localhost(server2:13075):41003' in
> java.lang.Thread.run(Thread.java:748)
> at
> org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:90)
> at
> org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:562)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1249)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986){noformat}
> The {{AssertionError}} thrown by {{DiskVersionTag.replaceNullIDs()}} is not
> handled by any of the calling methods, which leads to the GII failing without
> attempting to retry, and does not decrement the getInitialImagesInProgress
> stat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8494) CI Failure: Tomcat7SessionsTest.setupClass fails due to java.net.BindException: Address already in use
[
https://issues.apache.org/jira/browse/GEODE-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519081#comment-17519081
]
Geode Integration commented on GEODE-8494:
--
Seen on support/1.14 in [windows-integration-test-openjdk11
#43|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/windows-integration-test-openjdk11/builds/43]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0948/test-results/integrationTest/1649329530/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0948/test-artifacts/1649329530/windows-integrationtestfiles-openjdk11-1.14.5-build.0948.tgz].
> CI Failure: Tomcat7SessionsTest.setupClass fails due to
> java.net.BindException: Address already in use
> --
>
> Key: GEODE-8494
> URL: https://issues.apache.org/jira/browse/GEODE-8494
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.3, 1.13.3, 1.14.0
>Reporter: Donal Evans
>Priority: Major
>
> This is possibly just an unlucky port collision due to multiple tests being
> run at the same time.
> {noformat}
> org.apache.geode.modules.session.Tomcat7SessionsTest > classMethod FAILED
> org.apache.catalina.LifecycleException: service.getName(): "null";
> Protocol handler start failed
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:986)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.startup.Embedded.startInternal(Embedded.java:781)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.geode.modules.session.EmbeddedTomcat.startContainer(EmbeddedTomcat.java:98)
> at
> org.apache.geode.modules.session.AbstractSessionsTest.setupServer(AbstractSessionsTest.java:71)
> at
> org.apache.geode.modules.session.Tomcat7SessionsTest.setupClass(Tomcat7SessionsTest.java:36)
> Caused by:
> java.net.BindException: Address already in use: NET_Bind :49811
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:414)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:767)
> at
> org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:482)
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:979)
> ... 6 more
> Caused by:
> java.net.BindException: Address already in use: NET_Bind
> at java.net.PlainSocketImpl.bind0(Native Method)
> at
> java.net.PlainSocketImpl.socketBind(PlainSocketImpl.java:132)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:436)
> at java.net.ServerSocket.bind(ServerSocket.java:395)
> at java.net.ServerSocket.(ServerSocket.java:257)
> at java.net.ServerSocket.(ServerSocket.java:201)
> at
> org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:401)
> ... 9 more
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-results/integrationTest/1600111592/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-artifacts/1600111592/windows-integrationtestfiles-OpenJDK11-1.14.0-build.0330.tgz]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10077) wan-copy region command does not prevent callbacks to be executed on the remote site
[ https://issues.apache.org/jira/browse/GEODE-10077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519101#comment-17519101 ] ASF subversion and git services commented on GEODE-10077: - Commit 3889df2803c7d7313a6040229e2de401a890f8e4 in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3889df2803 ] GEODE-10077: Avoid callbacks in wan-copy region (#7391) The wan-copy region command does not always prevent that callbacks are executed at the remote site for the entries copied. The value set by the wan-copy region command for generateCallbacks to false in the events sent via the gateway sender was not being propagated by the server that received the events in the remote site (via the gateway receiver) when proxying the put by means of a PutMessage or UpdateMessage in order to send the event to the server with the primary bucket or to replicate the put in case of more than one replica in the region. The flags in the PutMessage and UpdateMessage have been used to propagate the value of generateCallbacks. > wan-copy region command does not prevent callbacks to be executed on the > remote site > > > Key: GEODE-10077 > URL: https://issues.apache.org/jira/browse/GEODE-10077 > Project: Geode > Issue Type: Bug > Components: gfsh, wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The wan-copy region command does not always prevent that callbacks are > executed at the remote site for the entries copied. > For example, if the remote site has more than one server and the gateway > receiver that gets the entries copied does not host the primary bucket of the > entry received, it will send the put operation to the server than hosts the > primary bucket and on this server, callbacks will be executed, provoking, for > example, that if a gateway sender is configured for the region, the event > will be sent by that gateway sender in the remote site. > Also, if the remote site has more than one server and the region has at least > one replica (either because it is a replicated region or because it is a > partitioned region with number of replicas greater than 1) then servers in > the remote site that receive an UpdateMessage from the server that received > the copied entry via the gateway receiver, would execute the callbacks, > provoking, like in the above case that if a gateway sender is configured for > the region, the event will be sent by that gateway sender in the remote site. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7460) CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs ForcedDisconnectException Failure
[ https://issues.apache.org/jira/browse/GEODE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519137#comment-17519137 ] Geode Integration commented on GEODE-7460: -- Seen on support/1.13 in [distributed-test-openjdk8 #45|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/distributed-test-openjdk8/builds/45] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0675/test-results/distributedTest/1649360039/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0675/test-artifacts/1649360039/distributedtestfiles-openjdk8-1.13.9-build.0675.tgz]. > CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs > ForcedDisconnectException Failure > --- > > Key: GEODE-7460 > URL: https://issues.apache.org/jira/browse/GEODE-7460 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.13.0, 1.14.0 >Reporter: Robert Houghton >Assignee: Bill Burcham >Priority: Major > Fix For: 1.12.3, 1.13.3 > > Time Spent: 20m > Remaining Estimate: 0h > > From the failing job: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-results/distributedTest/1573784422/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-artifacts/1573784422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0016.tgz > DistributedTest failure due to exception: > org.apache.geode.distributed.DistributedMemberDUnitTest > testGroupsInAllVMs > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run in VM 0 running > on Host 3e09f1029b44 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.distributed.DistributedMemberDUnitTest.testGroupsInAllVMs(DistributedMemberDUnitTest.java:333) > Caused by: > org.apache.geode.SystemConnectException: One or more peers generated > exceptions during connection attempt > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1625) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:759) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:136) > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3009) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:269) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:181) > at > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run(DistributedMemberDUnitTest.java:339) > Caused by: > > org.apache.geode.distributed.DistributedSystemDisconnectedException: > DistributedSystem is shutting down, caused by > org.apache.geode.ForcedDisconnectException: Exiting due to possible network > partition event due to loss of 1 cache processes: > [172.17.0.14(myName:1):41001] > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1591) > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1751) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2058) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1985) > at > org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:74) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1
[jira] [Commented] (GEODE-10217) Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519143#comment-17519143
]
Geode Integration commented on GEODE-10217:
---
Seen in [unit-test-openjdk8
#276|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/unit-test-openjdk8/builds/276]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1078/test-results/test/1649274007/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1078/test-artifacts/1649274007/unittestfiles-openjdk8-1.15.0-build.1078.tgz].
> Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
> -
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
> Byte Buddy could not instrument all classes within the mock's type hierarchy.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
> 10:19:40at
> org.mockito.intern
[jira] [Updated] (GEODE-10120) Update Ruby Dependencies
[ https://issues.apache.org/jira/browse/GEODE-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10120: --- Labels: pull-request-available (was: ) > Update Ruby Dependencies > > > Key: GEODE-10120 > URL: https://issues.apache.org/jira/browse/GEODE-10120 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > We should update out of date ruby dependencies > So that we keep on top of build process and security updates -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10120) Update Ruby Dependencies
[ https://issues.apache.org/jira/browse/GEODE-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519150#comment-17519150 ] ASF subversion and git services commented on GEODE-10120: - Commit 99df0109cd434a22a3ddf0186c5150a7756f7bac in geode-native's branch refs/heads/develop from M. Oleske [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=99df0109c ] GEODE-10120: Bump ruby dependencies (#945) * Bump addressable from 2.7.0 to 2.8.0 in /docs/geode-native-book-cpp Bumps [addressable](https://github.com/sporkmonger/addressable) from 2.7.0 to 2.8.0. - [Release notes](https://github.com/sporkmonger/addressable/releases) - [Changelog](https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md) - [Commits](https://github.com/sporkmonger/addressable/compare/addressable-2.7.0...addressable-2.8.0) --- updated-dependencies: - dependency-name: addressable dependency-type: indirect ... Signed-off-by: dependabot[bot] * Bump addressable from 2.7.0 to 2.8.0 in /docs/geode-native-book-dotnet Bumps [addressable](https://github.com/sporkmonger/addressable) from 2.7.0 to 2.8.0. - [Release notes](https://github.com/sporkmonger/addressable/releases) - [Changelog](https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md) - [Commits](https://github.com/sporkmonger/addressable/compare/addressable-2.7.0...addressable-2.8.0) --- updated-dependencies: - dependency-name: addressable dependency-type: indirect ... Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> > Update Ruby Dependencies > > > Key: GEODE-10120 > URL: https://issues.apache.org/jira/browse/GEODE-10120 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > We should update out of date ruby dependencies > So that we keep on top of build process and security updates -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10186) CI failure: RedundancyLevelPart1DUnitTest > testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for getClientProxies() to return more than 0 objec
[
https://issues.apache.org/jira/browse/GEODE-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519151#comment-17519151
]
Geode Integration commented on GEODE-10186:
---
Seen in [distributed-test-openjdk8
#283|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/283]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1077/test-results/distributedTest/1649271644/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1077/test-artifacts/1649271644/distributedtestfiles-openjdk8-1.15.0-build.1077.tgz].
> CI failure: RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for
> getClientProxies() to return more than 0 objects
> -
>
> Key: GEODE-10186
> URL: https://issues.apache.org/jira/browse/GEODE-10186
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Failed here: [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14277358]
>
> {noformat}
> > Task :geode-core:distributedTest
> RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest$$Lambda$543/510122765.run
> in VM 2 running on Host
> heavy-lifter-f58561da-caf9-5bc0-a7fa-f938c3fd1e51.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU(RedundancyLevelPart1DUnitTest.java:284)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest
> that uses org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier
> Expecting actual:
> 0
> to be greater than:
> 0
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.verifyInterestRegistration(RedundancyLevelPart1DUnitTest.java:505)
> Caused by:
> java.lang.AssertionError:
> Expecting actual:
> 0
> to be greater than:
> 0
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.lambda$verifyInterestRegistration$19(RedundancyLevelPart1DUnitTest.java:506)
> 8352 tests completed, 1 failed, 414 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-results/distributedTest/1648331031/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-artifacts/1648331031/distributedtestfiles-openjdk8-1.15.0-build.1033.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10120) Update Ruby Dependencies
[ https://issues.apache.org/jira/browse/GEODE-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519149#comment-17519149 ] ASF GitHub Bot commented on GEODE-10120: moleske merged PR #945: URL: https://github.com/apache/geode-native/pull/945 > Update Ruby Dependencies > > > Key: GEODE-10120 > URL: https://issues.apache.org/jira/browse/GEODE-10120 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > > We should update out of date ruby dependencies > So that we keep on top of build process and security updates -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10221) RedisList does not set memory usage correctly when creating a copy
[
https://issues.apache.org/jira/browse/GEODE-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519152#comment-17519152
]
ASF subversion and git services commented on GEODE-10221:
-
Commit 4989b9ae828a8595510d956b303e2981d44c5773 in geode's branch
refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4989b9ae82 ]
GEODE-10221: Fix sizing when creating a RedisList copy (#7568)
- The size must be updated as part of cloning an existing list.
> RedisList does not set memory usage correctly when creating a copy
> --
>
> Key: GEODE-10221
> URL: https://issues.apache.org/jira/browse/GEODE-10221
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> Since adding a constructor to {{RedisList}} that takes another list in order
> to create a copy, we don't update the memory overhead of the new list
> correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10217) Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519154#comment-17519154
]
Geode Integration commented on GEODE-10217:
---
Seen in [unit-test-openjdk8
#282|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/unit-test-openjdk8/builds/282]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1084/test-results/test/1649359140/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1084/test-artifacts/1649359140/unittestfiles-openjdk8-1.15.0-build.1084.tgz].
> Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
> -
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
> Byte Buddy could not instrument all classes within the mock's type hierarchy.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
> 10:19:40at
> org.mockito.intern
[jira] [Commented] (GEODE-10186) CI failure: RedundancyLevelPart1DUnitTest > testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for getClientProxies() to return more than 0 objec
[
https://issues.apache.org/jira/browse/GEODE-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519155#comment-17519155
]
Geode Integration commented on GEODE-10186:
---
Seen in [distributed-test-openjdk8
#287|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/287]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/distributedTest/1649310464/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649310464/distributedtestfiles-openjdk8-1.15.0-build.1082.tgz].
> CI failure: RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for
> getClientProxies() to return more than 0 objects
> -
>
> Key: GEODE-10186
> URL: https://issues.apache.org/jira/browse/GEODE-10186
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Failed here: [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14277358]
>
> {noformat}
> > Task :geode-core:distributedTest
> RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest$$Lambda$543/510122765.run
> in VM 2 running on Host
> heavy-lifter-f58561da-caf9-5bc0-a7fa-f938c3fd1e51.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU(RedundancyLevelPart1DUnitTest.java:284)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest
> that uses org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier
> Expecting actual:
> 0
> to be greater than:
> 0
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.verifyInterestRegistration(RedundancyLevelPart1DUnitTest.java:505)
> Caused by:
> java.lang.AssertionError:
> Expecting actual:
> 0
> to be greater than:
> 0
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.lambda$verifyInterestRegistration$19(RedundancyLevelPart1DUnitTest.java:506)
> 8352 tests completed, 1 failed, 414 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-results/distributedTest/1648331031/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-artifacts/1648331031/distributedtestfiles-openjdk8-1.15.0-build.1033.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9980) Startup of Locator or Server should fail fast if geode.enableGlobalSerialFilter is enabled but fails configuration
[
https://issues.apache.org/jira/browse/GEODE-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9980:
Fix Version/s: (was: 1.12.10)
(was: 1.13.9)
> Startup of Locator or Server should fail fast if
> geode.enableGlobalSerialFilter is enabled but fails configuration
> --
>
> Key: GEODE-9980
> URL: https://issues.apache.org/jira/browse/GEODE-9980
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.14.5, 1.15.0
>
>
> The following error conditions need better handling which includes handling
> of all errors consistently and cause the startup of a Locator or Server to
> fail if it's unable to honor the setting of
> {{-Dgeode.enableGlobalSerialFilter=true}} for any reason. Currently, if
> {{-Dgeode.enableGlobalSerialFilter=true}} is specified but Geode is unable to
> create a global serial filter, then it will will log a warning and continue
> running. A user may easily miss that log statement and believe that the JVM
> is running with a properly configured serialization filter.
> 1) The user is trying to secure the JVM very thoroughly and accidentally
> specifies both {{-Djdk.serialFilter}} and
> {{-Dgeode.enableGlobalSerialFilter}}.
> 2) The user runs some non-Geode code in the same JVM that invokes
> {{ObjectInputFilter.Config.setFilter(...)}} directly.
> 3) The user is using a version of Java 8 prior to 8u121 (the release that
> first added {{sun.misc.ObjectInputFilter}}) and specifies
> {{-Dgeode.enableGlobalSerialFilter=true}}. Also, the same behavior occurs if
> they do NOT specify enabling that property.
> 4) {{LocatorLauncher}} or {{ServerLauncher}} is started in a JVM that has
> already created at least one {{ObjectInputStream}} which will cause
> {{ObjectInputFilter.Config.setFilter(...)}} to fail.
> 5) {{LocatorLauncher}} or {{ServerLauncher}} is started in a Java 8 JVM that
> is not based on OpenJDK (ie {{sun.misc.ObjectInputFilter}} does not exist).
> 6) {{LocatorLauncher}} or {{ServerLauncher}} is started in an unforeseen
> environment that causes invocation of
> {{ObjectInputFilter.Config.setFilter(...)}} via Java Reflection to throw
> {{IllegalAccessException}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10217) Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519164#comment-17519164
]
Owen Nichols commented on GEODE-10217:
--
On March 16 we [bumped mockito from 4.3.1 to
4.4.0|https://github.com/apache/geode/commit/9ff27b37cf5cc7a97700c64c77a28eefe8ae9d4a]
> Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
> -
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
> Byte Buddy could not instrument all classes within the mock's type hierarchy.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:389)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:349)
> 10:19:40at
> org.mockito.internal.creation
[jira] [Comment Edited] (GEODE-10217) Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519164#comment-17519164
]
Owen Nichols edited comment on GEODE-10217 at 4/7/22 8:58 PM:
--
On March 16 we [bumped mockito from 4.3.1 to
4.4.0|https://github.com/apache/geode/commit/9ff27b37cf5cc7a97700c64c77a28eefe8ae9d4a]
but the stack trace also mentioned an NPE in ThreadLocalRandom, seems like
there was some other issue with that recently...?
was (Author: onichols-pivotal):
On March 16 we [bumped mockito from 4.3.1 to
4.4.0|https://github.com/apache/geode/commit/9ff27b37cf5cc7a97700c64c77a28eefe8ae9d4a]
> Mockito Unable to Mock org.apache.geode.internal.cache.DiskRegion
> -
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
> Byte Buddy could not instrument all classes within the mock's type hierarchy.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
> 10:19:40at
> org.mockito.
[jira] [Updated] (GEODE-10146) GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10146:
---
Labels: Java17 pull-request-available (was: Java17)
> GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
> --
>
> Key: GEODE-10146
> URL: https://issues.apache.org/jira/browse/GEODE-10146
> Project: Geode
> Issue Type: Improvement
> Components: build
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Priority: Major
> Labels: Java17, pull-request-available
>
> On JDK 17, GradleBuildWithGeodeCoreAcceptanceTest throws an exception
> ultimately caused by: "NoClassDefFoundError: Could not initialize class
> org.codehaus.groovy.reflection.ReflectionCache"
> Example failure (in a PR precheck):
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7457/test-results/acceptanceTest/1647647868/classes/org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.html#testBasicGradleBuild]
> {noformat}
> org.gradle.tooling.BuildException: Could not execute build using Gradle
> distribution 'https://services.gradle.org/distributions/gradle-5.1.1-bin.zip'.
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:51)
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:29)
> at
> org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:41)
> at
> org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:57)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
> at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
> at java.lang.Thread.run(Thread.java:833)
> at
> org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
> at
> org.gradle.tooling.internal.consumer.DefaultBuildLauncher.run(DefaultBuildLauncher.java:77)
> at
> org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.testBasicGradleBuild(GradleBuildWithGeodeCoreAcceptanceTest.java:71)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> at
> org.junit.vintage.engine.VintageTestEngine.execut
[jira] [Updated] (GEODE-10146) GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-10146:
---
Component/s: tests
(was: build)
> GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
> --
>
> Key: GEODE-10146
> URL: https://issues.apache.org/jira/browse/GEODE-10146
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Priority: Major
> Labels: Java17, pull-request-available
>
> On JDK 17, GradleBuildWithGeodeCoreAcceptanceTest throws an exception
> ultimately caused by: "NoClassDefFoundError: Could not initialize class
> org.codehaus.groovy.reflection.ReflectionCache"
> Example failure (in a PR precheck):
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7457/test-results/acceptanceTest/1647647868/classes/org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.html#testBasicGradleBuild]
> {noformat}
> org.gradle.tooling.BuildException: Could not execute build using Gradle
> distribution 'https://services.gradle.org/distributions/gradle-5.1.1-bin.zip'.
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:51)
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:29)
> at
> org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:41)
> at
> org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:57)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
> at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
> at java.lang.Thread.run(Thread.java:833)
> at
> org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
> at
> org.gradle.tooling.internal.consumer.DefaultBuildLauncher.run(DefaultBuildLauncher.java:77)
> at
> org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.testBasicGradleBuild(GradleBuildWithGeodeCoreAcceptanceTest.java:71)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChil
[jira] [Assigned] (GEODE-10146) GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-10146:
--
Assignee: Dale Emery
> GradleBuildWithGeodeCoreAcceptanceTest fails on JDK 17
> --
>
> Key: GEODE-10146
> URL: https://issues.apache.org/jira/browse/GEODE-10146
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: Java17, pull-request-available
>
> On JDK 17, GradleBuildWithGeodeCoreAcceptanceTest throws an exception
> ultimately caused by: "NoClassDefFoundError: Could not initialize class
> org.codehaus.groovy.reflection.ReflectionCache"
> Example failure (in a PR precheck):
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7457/test-results/acceptanceTest/1647647868/classes/org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.html#testBasicGradleBuild]
> {noformat}
> org.gradle.tooling.BuildException: Could not execute build using Gradle
> distribution 'https://services.gradle.org/distributions/gradle-5.1.1-bin.zip'.
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:51)
> at
> org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:29)
> at
> org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:41)
> at
> org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:57)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
> at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
> at java.lang.Thread.run(Thread.java:833)
> at
> org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
> at
> org.gradle.tooling.internal.consumer.DefaultBuildLauncher.run(DefaultBuildLauncher.java:77)
> at
> org.apache.geode.management.internal.rest.GradleBuildWithGeodeCoreAcceptanceTest.testBasicGradleBuild(GradleBuildWithGeodeCoreAcceptanceTest.java:71)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> at
> org.junit.vintage.engine.VintageTestEngine.execu
[jira] [Commented] (GEODE-10131) Remove unused but set variable
[ https://issues.apache.org/jira/browse/GEODE-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519188#comment-17519188 ] ASF GitHub Bot commented on GEODE-10131: moleske commented on PR #947: URL: https://github.com/apache/geode-native/pull/947#issuecomment-1092249552 @pdxcodemonkey I think the ubuntu fixes that were made need to be copied to LGTM as it seems to be failing for the same reason over there > Remove unused but set variable > -- > > Key: GEODE-10131 > URL: https://issues.apache.org/jira/browse/GEODE-10131 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > When on AppleClang 13.1.6.13160021 on macOS 12.3, native client fails to > compile due to warning as error -Wunused-but-set-variable > Remove the offending lines to compile -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9615) CI Failure: Acceptance Tests fails with exit value 1 from start locator
[
https://issues.apache.org/jira/browse/GEODE-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519198#comment-17519198
]
Geode Integration commented on GEODE-9615:
--
Seen in [windows-acceptance-test-openjdk8
#274|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-acceptance-test-openjdk8/builds/274]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/acceptanceTest/1649289675/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649289675/windows-acceptancetestfiles-openjdk8-1.15.0-build.1081.tgz].
> CI Failure: Acceptance Tests fails with exit value 1 from start locator
> ---
>
> Key: GEODE-9615
> URL: https://issues.apache.org/jira/browse/GEODE-9615
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Priority: Major
>
> {code:java}
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --host=localhost --port=20608]] expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port(StatusLocatorExitCodeAcceptanceTest.java:128)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > offlineStatusCommandShouldSucceedWhenConnected_locator_dir FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --dir=/tmp/junit11722670533134972918/member-controller/locator-chase-obedient-cake]]
> expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.offlineStatusCommandShouldSucceedWhenConnected_locator_dir(StatusLocatorExitCodeAcceptanceTest.java:140)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_name FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --name=locator-chase-obedient-cake]] expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rul
[jira] [Updated] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10217:
Summary: NullPointerException or NoClassDefFoundError in ThreadLocalRandom
causes multiple test failures (was: Mockito Unable to Mock
org.apache.geode.internal.cache.DiskRegion)
> NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes
> multiple test failures
> ---
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
> Byte Buddy could not instrument all classes within the mock's type hierarchy.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:389)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:349)
> 10:1
[jira] [Updated] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10217:
Description:
Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
Byte Buddy could not instrument all classes within the mock's type hierarchy.
{noformat}
DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
10:19:40org.mockito.exceptions.base.MockitoException:
10:19:40Mockito cannot mock this class: class
org.apache.geode.internal.cache.DiskRegion.
10:19:40
10:19:40If you're not sure why you're getting this error, please report to
the mailing list.
10:19:40
10:19:40
10:19:40Java : 1.8
10:19:40JVM vendor name: BellSoft
10:19:40JVM vendor version : 25.322-b06
10:19:40JVM name : OpenJDK 64-Bit Server VM
10:19:40JVM version: 1.8.0_322-b06
10:19:40JVM info : mixed mode
10:19:40OS name: Linux
10:19:40OS version : 5.4.0-1069-gcp
10:19:40
10:19:40
10:19:40You are seeing this disclaimer because Mockito is configured to
create inlined mocks.
10:19:40You can learn about inline mocks and their limitations under item
#39 of the Mockito class javadoc.
10:19:40
10:19:40Underlying exception :
org.mockito.exceptions.base.MockitoException: Could not modify all classes
[class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at
org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
10:19:40
10:19:40Caused by:
10:19:40org.mockito.exceptions.base.MockitoException: Could not modify
all classes [class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.IllegalStateException:
10:19:40Byte Buddy could not instrument all classes within the
mock's type hierarchy
10:19:40
10:19:40This problem should never occur for javac-compiled classes.
This problem has been observed for classes that are:
10:19:40 - Compiled by older versions of scalac
10:19:40 - Classes that are part of the Android distribution
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:389)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:349)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:328)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
10:19:40at
org.mockito.internal.util.MockUtil.createMock(MockUtil.java:53)
10:19:40at
org.mockito.internal.MockitoCore.mock(MockitoCore.java:96)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1965)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1880)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.ExceptionInInitializerError
10:19:40at
java.util.concur
[jira] [Updated] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10217:
Description:
Mokito cannot mock DiskRegion, DiskRegionView, and AbstractDiskRegion because
Byte Buddy could not instrument all classes within the mock's type hierarchy.
{noformat}
DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
10:19:40org.mockito.exceptions.base.MockitoException:
10:19:40Mockito cannot mock this class: class
org.apache.geode.internal.cache.DiskRegion.
10:19:40
10:19:40If you're not sure why you're getting this error, please report to
the mailing list.
10:19:40
10:19:40
10:19:40Java : 1.8
10:19:40JVM vendor name: BellSoft
10:19:40JVM vendor version : 25.322-b06
10:19:40JVM name : OpenJDK 64-Bit Server VM
10:19:40JVM version: 1.8.0_322-b06
10:19:40JVM info : mixed mode
10:19:40OS name: Linux
10:19:40OS version : 5.4.0-1069-gcp
10:19:40
10:19:40
10:19:40You are seeing this disclaimer because Mockito is configured to
create inlined mocks.
10:19:40You can learn about inline mocks and their limitations under item
#39 of the Mockito class javadoc.
10:19:40
10:19:40Underlying exception :
org.mockito.exceptions.base.MockitoException: Could not modify all classes
[class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at
org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
10:19:40
10:19:40Caused by:
10:19:40org.mockito.exceptions.base.MockitoException: Could not modify
all classes [class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.IllegalStateException:
10:19:40Byte Buddy could not instrument all classes within the
mock's type hierarchy
10:19:40
10:19:40This problem should never occur for javac-compiled classes.
This problem has been observed for classes that are:
10:19:40 - Compiled by older versions of scalac
10:19:40 - Classes that are part of the Android distribution
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:389)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:349)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:328)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
10:19:40at
org.mockito.internal.util.MockUtil.createMock(MockUtil.java:53)
10:19:40at
org.mockito.internal.MockitoCore.mock(MockitoCore.java:96)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1965)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1880)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.ExceptionInInitializerError
10:19:40at
java.util.concur
[jira] [Updated] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10217:
Description:
The below stack traces were seen in the unit-test-openjdk8 job in the pipeline.
In addition to the two failures shown, multiple other failures due to
{{NoClassDefFoundError}} for {{ThreadLocalRandom}} were also present.
{noformat}
DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
10:19:40org.mockito.exceptions.base.MockitoException:
10:19:40Mockito cannot mock this class: class
org.apache.geode.internal.cache.DiskRegion.
10:19:40
10:19:40If you're not sure why you're getting this error, please report to
the mailing list.
10:19:40
10:19:40
10:19:40Java : 1.8
10:19:40JVM vendor name: BellSoft
10:19:40JVM vendor version : 25.322-b06
10:19:40JVM name : OpenJDK 64-Bit Server VM
10:19:40JVM version: 1.8.0_322-b06
10:19:40JVM info : mixed mode
10:19:40OS name: Linux
10:19:40OS version : 5.4.0-1069-gcp
10:19:40
10:19:40
10:19:40You are seeing this disclaimer because Mockito is configured to
create inlined mocks.
10:19:40You can learn about inline mocks and their limitations under item
#39 of the Mockito class javadoc.
10:19:40
10:19:40Underlying exception :
org.mockito.exceptions.base.MockitoException: Could not modify all classes
[class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at
org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
10:19:40
10:19:40Caused by:
10:19:40org.mockito.exceptions.base.MockitoException: Could not modify
all classes [class org.apache.geode.internal.cache.DiskRegion, interface
org.apache.geode.internal.cache.persistence.DiskRegionView, class
org.apache.geode.internal.cache.AbstractDiskRegion]
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.IllegalStateException:
10:19:40Byte Buddy could not instrument all classes within the
mock's type hierarchy
10:19:40
10:19:40This problem should never occur for javac-compiled classes.
This problem has been observed for classes that are:
10:19:40 - Compiled by older versions of scalac
10:19:40 - Classes that are part of the Android distribution
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
10:19:40at
net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
10:19:40at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
10:19:40at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:389)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:349)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:328)
10:19:40at
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
10:19:40at
org.mockito.internal.util.MockUtil.createMock(MockUtil.java:53)
10:19:40at
org.mockito.internal.MockitoCore.mock(MockitoCore.java:96)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1965)
10:19:40at org.mockito.Mockito.mock(Mockito.java:1880)
10:19:40... 1 more
10:19:40
10:19:40Caused by:
10:19:40java.lang.ExceptionIn
[jira] [Commented] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures
[
https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519220#comment-17519220
]
Geode Integration commented on GEODE-10217:
---
Seen in [unit-test-openjdk8
#279|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/unit-test-openjdk8/builds/279]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/test/1649280496/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649280496/unittestfiles-openjdk8-1.15.0-build.1081.tgz].
> NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes
> multiple test failures
> ---
>
> Key: GEODE-10217
> URL: https://issues.apache.org/jira/browse/GEODE-10217
> Project: Geode
> Issue Type: Bug
> Components: core, tests
>Reporter: Patrick Johnsn
>Priority: Major
>
> The below stack traces were seen in the unit-test-openjdk8 job in the
> pipeline. In addition to the two failures shown, multiple other failures due
> to {{NoClassDefFoundError}} for {{ThreadLocalRandom}} were also present.
> {noformat}
> DiskEntryHelperTest > doSynchronousWriteReturnsTrueWhenDiskRegionIsSync FAILED
> 10:19:40org.mockito.exceptions.base.MockitoException:
> 10:19:40Mockito cannot mock this class: class
> org.apache.geode.internal.cache.DiskRegion.
> 10:19:40
> 10:19:40If you're not sure why you're getting this error, please report
> to the mailing list.
> 10:19:40
> 10:19:40
> 10:19:40Java : 1.8
> 10:19:40JVM vendor name: BellSoft
> 10:19:40JVM vendor version : 25.322-b06
> 10:19:40JVM name : OpenJDK 64-Bit Server VM
> 10:19:40JVM version: 1.8.0_322-b06
> 10:19:40JVM info : mixed mode
> 10:19:40OS name: Linux
> 10:19:40OS version : 5.4.0-1069-gcp
> 10:19:40
> 10:19:40
> 10:19:40You are seeing this disclaimer because Mockito is configured to
> create inlined mocks.
> 10:19:40You can learn about inline mocks and their limitations under item
> #39 of the Mockito class javadoc.
> 10:19:40
> 10:19:40Underlying exception :
> org.mockito.exceptions.base.MockitoException: Could not modify all classes
> [class org.apache.geode.internal.cache.DiskRegion, interface
> org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> org.apache.geode.internal.cache.entries.DiskEntryHelperTest.(DiskEntryHelperTest.java:44)
> 10:19:40
> 10:19:40Caused by:
> 10:19:40org.mockito.exceptions.base.MockitoException: Could not
> modify all classes [class org.apache.geode.internal.cache.DiskRegion,
> interface org.apache.geode.internal.cache.persistence.DiskRegionView, class
> org.apache.geode.internal.cache.AbstractDiskRegion]
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40... 1 more
> 10:19:40
> 10:19:40Caused by:
> 10:19:40java.lang.IllegalStateException:
> 10:19:40Byte Buddy could not instrument all classes within the
> mock's type hierarchy
> 10:19:40
> 10:19:40This problem should never occur for javac-compiled
> classes. This problem has been observed for classes that are:
> 10:19:40 - Compiled by older versions of scalac
> 10:19:40 - Classes that are part of the Android distribution
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:213)
> 10:19:40at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:157)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:371)
> 10:19:40at
> net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:179)
> 10:19:40at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:382)
> 10:19:40at
> org.mockito.internal.creation.bytebud
[jira] [Commented] (GEODE-9615) CI Failure: Acceptance Tests fails with exit value 1 from start locator
[
https://issues.apache.org/jira/browse/GEODE-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519226#comment-17519226
]
Geode Integration commented on GEODE-9615:
--
Seen in [windows-acceptance-test-openjdk8
#271|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-acceptance-test-openjdk8/builds/271]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1077/test-results/acceptanceTest/1649271706/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1077/test-artifacts/1649271706/windows-acceptancetestfiles-openjdk8-1.15.0-build.1077.tgz].
> CI Failure: Acceptance Tests fails with exit value 1 from start locator
> ---
>
> Key: GEODE-9615
> URL: https://issues.apache.org/jira/browse/GEODE-9615
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Priority: Major
>
> {code:java}
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --host=localhost --port=20608]] expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port(StatusLocatorExitCodeAcceptanceTest.java:128)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > offlineStatusCommandShouldSucceedWhenConnected_locator_dir FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --dir=/tmp/junit11722670533134972918/member-controller/locator-chase-obedient-cake]]
> expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.offlineStatusCommandShouldSucceedWhenConnected_locator_dir(StatusLocatorExitCodeAcceptanceTest.java:140)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_name FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --name=locator-chase-obedient-cake]] expected:<[0]> but was:<[1]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rul
[jira] [Updated] (GEODE-10223) BlockingCommandListenerTest > testTimeoutIsAdjusted fails on Windows due to timeout not changing
[
https://issues.apache.org/jira/browse/GEODE-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10223:
--
Labels: needsTriage (was: )
> BlockingCommandListenerTest > testTimeoutIsAdjusted fails on Windows due to
> timeout not changing
>
>
> Key: GEODE-10223
> URL: https://issues.apache.org/jira/browse/GEODE-10223
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> > Task :geode-for-redis:integrationTest
> BlockingCommandListenerTest > testTimeoutIsAdjusted FAILED
> java.lang.AssertionError:
> Expecting actual:
> 1.0
> to be less than:
> 1.0
> at
> org.apache.geode.redis.internal.eventing.BlockingCommandListenerTest.testTimeoutIsAdjusted(BlockingCommandListenerTest.java:61){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/integrationTest/1649299123/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649299123/windows-integrationtestfiles-openjdk11-1.15.0-build.1081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10223) BlockingCommandListenerTest > testTimeoutIsAdjusted fails on Windows due to timeout not changing
Donal Evans created GEODE-10223:
---
Summary: BlockingCommandListenerTest > testTimeoutIsAdjusted fails
on Windows due to timeout not changing
Key: GEODE-10223
URL: https://issues.apache.org/jira/browse/GEODE-10223
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
{noformat}
> Task :geode-for-redis:integrationTest
BlockingCommandListenerTest > testTimeoutIsAdjusted FAILED
java.lang.AssertionError:
Expecting actual:
1.0
to be less than:
1.0
at
org.apache.geode.redis.internal.eventing.BlockingCommandListenerTest.testTimeoutIsAdjusted(BlockingCommandListenerTest.java:61){noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/integrationTest/1649299123/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
report artifacts from this job are available
at:http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649299123/windows-integrationtestfiles-openjdk11-1.15.0-build.1081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10223) BlockingCommandListenerTest > testTimeoutIsAdjusted fails on Windows due to timeout not changing
[
https://issues.apache.org/jira/browse/GEODE-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519227#comment-17519227
]
Geode Integration commented on GEODE-10223:
---
Seen in [windows-integration-test-openjdk11
#262|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-integration-test-openjdk11/builds/262]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/integrationTest/1649299123/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649299123/windows-integrationtestfiles-openjdk11-1.15.0-build.1081.tgz].
> BlockingCommandListenerTest > testTimeoutIsAdjusted fails on Windows due to
> timeout not changing
>
>
> Key: GEODE-10223
> URL: https://issues.apache.org/jira/browse/GEODE-10223
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> > Task :geode-for-redis:integrationTest
> BlockingCommandListenerTest > testTimeoutIsAdjusted FAILED
> java.lang.AssertionError:
> Expecting actual:
> 1.0
> to be less than:
> 1.0
> at
> org.apache.geode.redis.internal.eventing.BlockingCommandListenerTest.testTimeoutIsAdjusted(BlockingCommandListenerTest.java:61){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-results/integrationTest/1649299123/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1081/test-artifacts/1649299123/windows-integrationtestfiles-openjdk11-1.15.0-build.1081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10224) geode-connectors:acceptanceTest task hang in CI with no tests started
[
https://issues.apache.org/jira/browse/GEODE-10224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10224:
--
Labels: needsTriage (was: )
> geode-connectors:acceptanceTest task hang in CI with no tests started
> -
>
> Key: GEODE-10224
> URL: https://issues.apache.org/jira/browse/GEODE-10224
> Project: Geode
> Issue Type: Bug
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> A hang was observed in a CI run of acceptance-test-openjdk8:
> {noformat}
> 20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
> 20:37:55> Task :geode-assembly:acceptanceTest
> 21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
> 21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
> 21:44:13> Task :geode-common:acceptanceTestClasses UP-TO-DATE
> 21:44:13> Task :geode-common:acceptanceTest NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:compileAcceptanceTestJava NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:processAcceptanceTestResources
> NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:acceptanceTestClasses UP-TO-DATE
> 21:44:13> Task :geode-concurrency-test:acceptanceTest NO-SOURCE
> 21:44:16> Task :geode-connectors:compileAcceptanceTestJava
> 21:44:16> Task :geode-connectors:processAcceptanceTestResources
> 21:44:16> Task :geode-connectors:acceptanceTestClasses
> 21:44:46> Task :geode-connectors:acceptanceTest
> 21:44:46
> timeout exceeded{noformat}
> The geode-common:acceptanceTest task was able to complete normally, but the
> test result artifacts for the run, linked below, show no
> acceptanceTest-progress.txt in the {{geode-connectors/build/acceptanceTest}}
> directory, and no output in
> {{{}geode-connectors/build/test-results/acceptanceTest/binary/output.bin{}}},
> indicating that no tests from geode-connectors were able to start.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10224) geode-connectors:acceptanceTest task hang in CI with no tests started
Donal Evans created GEODE-10224:
---
Summary: geode-connectors:acceptanceTest task hang in CI with no
tests started
Key: GEODE-10224
URL: https://issues.apache.org/jira/browse/GEODE-10224
Project: Geode
Issue Type: Bug
Components: ci
Affects Versions: 1.15.0
Reporter: Donal Evans
A hang was observed in a CI run of acceptance-test-openjdk8:
{noformat}
20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
20:37:55> Task :geode-assembly:acceptanceTest
21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-common:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-common:acceptanceTest NO-SOURCE
21:44:13> Task :geode-concurrency-test:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-concurrency-test:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-concurrency-test:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-concurrency-test:acceptanceTest NO-SOURCE
21:44:16> Task :geode-connectors:compileAcceptanceTestJava
21:44:16> Task :geode-connectors:processAcceptanceTestResources
21:44:16> Task :geode-connectors:acceptanceTestClasses
21:44:46> Task :geode-connectors:acceptanceTest
21:44:46
timeout exceeded{noformat}
The geode-common:acceptanceTest task was able to complete normally, but the
test result artifacts for the run, linked below, show no
acceptanceTest-progress.txt in the {{geode-connectors/build/acceptanceTest}}
directory, and no output in
{{{}geode-connectors/build/test-results/acceptanceTest/binary/output.bin{}}},
indicating that no tests from geode-connectors were able to start.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10224) geode-connectors:acceptanceTest task hang in CI with no tests started
[
https://issues.apache.org/jira/browse/GEODE-10224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10224:
Description:
A hang was observed in a CI run of acceptance-test-openjdk8:
{noformat}
20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
20:37:55> Task :geode-assembly:acceptanceTest
21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-common:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-common:acceptanceTest NO-SOURCE
21:44:13> Task :geode-concurrency-test:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-concurrency-test:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-concurrency-test:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-concurrency-test:acceptanceTest NO-SOURCE
21:44:16> Task :geode-connectors:compileAcceptanceTestJava
21:44:16> Task :geode-connectors:processAcceptanceTestResources
21:44:16> Task :geode-connectors:acceptanceTestClasses
21:44:46> Task :geode-connectors:acceptanceTest
21:44:46
timeout exceeded{noformat}
The geode-common:acceptanceTest task was able to complete normally, but the
test result artifacts for the run, linked below, show no
acceptanceTest-progress.txt in the {{geode-connectors/build/acceptanceTest}}
directory, and no output in
{{{}geode-connectors/build/test-results/acceptanceTest/binary/output.bin{}}},
indicating that no tests from geode-connectors were able to start.
A subsequent run of the job passed with no issue.
={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}= Test Results URI
={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}=
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/]
={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz]
was:
A hang was observed in a CI run of acceptance-test-openjdk8:
{noformat}
20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
20:37:55> Task :geode-assembly:acceptanceTest
21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-common:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-common:acceptanceTest NO-SOURCE
21:44:13> Task :geode-concurrency-test:compileAcceptanceTestJava NO-SOURCE
21:44:13> Task :geode-concurrency-test:processAcceptanceTestResources NO-SOURCE
21:44:13> Task :geode-concurrency-test:acceptanceTestClasses UP-TO-DATE
21:44:13> Task :geode-concurrency-test:acceptanceTest NO-SOURCE
21:44:16> Task :geode-connectors:compileAcceptanceTestJava
21:44:16> Task :geode-connectors:processAcceptanceTestResources
21:44:16> Task :geode-connectors:acceptanceTestClasses
21:44:46> Task :geode-connectors:acceptanceTest
21:44:46
timeout exceeded{noformat}
The geode-common:acceptanceTest task was able to complete normally, but the
test result artifacts for the run, linked below, show no
acceptanceTest-progress.txt in the {{geode-connectors/build/acceptanceTest}}
directory, and no output in
{{{}geode-connectors/build/test-results/acceptanceTest/binary/output.bin{}}},
indicating that no tests from geode-connectors were able to start.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz
> geode-connectors:acceptanceTest task hang in CI with no tests started
> -
>
> Key: GEODE-10224
> URL: https://issues.apache.org/jira/browse/GEODE-10224
> Project: Geode
> Issue Type: Bug
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> A hang was observed in a CI run of acceptance-test-openjdk8:
> {noformat}
> 20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
> 20:37:55> Task :geode-assembly:acceptanceTest
> 21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
> 21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
> 21:44
[jira] [Commented] (GEODE-10224) geode-connectors:acceptanceTest task hang in CI with no tests started
[
https://issues.apache.org/jira/browse/GEODE-10224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519234#comment-17519234
]
Geode Integration commented on GEODE-10224:
---
Seen in [acceptance-test-openjdk8
#270|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/270]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz].
> geode-connectors:acceptanceTest task hang in CI with no tests started
> -
>
> Key: GEODE-10224
> URL: https://issues.apache.org/jira/browse/GEODE-10224
> Project: Geode
> Issue Type: Bug
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> A hang was observed in a CI run of acceptance-test-openjdk8:
> {noformat}
> 20:37:25> Task :geode-deployment:geode-deployment-legacy:publishToMavenLocal
> 20:37:55> Task :geode-assembly:acceptanceTest
> 21:44:13> Task :geode-common:compileAcceptanceTestJava NO-SOURCE
> 21:44:13> Task :geode-common:processAcceptanceTestResources NO-SOURCE
> 21:44:13> Task :geode-common:acceptanceTestClasses UP-TO-DATE
> 21:44:13> Task :geode-common:acceptanceTest NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:compileAcceptanceTestJava NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:processAcceptanceTestResources
> NO-SOURCE
> 21:44:13> Task :geode-concurrency-test:acceptanceTestClasses UP-TO-DATE
> 21:44:13> Task :geode-concurrency-test:acceptanceTest NO-SOURCE
> 21:44:16> Task :geode-connectors:compileAcceptanceTestJava
> 21:44:16> Task :geode-connectors:processAcceptanceTestResources
> 21:44:16> Task :geode-connectors:acceptanceTestClasses
> 21:44:46> Task :geode-connectors:acceptanceTest
> 21:44:46
> timeout exceeded{noformat}
> The geode-common:acceptanceTest task was able to complete normally, but the
> test result artifacts for the run, linked below, show no
> acceptanceTest-progress.txt in the {{geode-connectors/build/acceptanceTest}}
> directory, and no output in
> {{{}geode-connectors/build/test-results/acceptanceTest/binary/output.bin{}}},
> indicating that no tests from geode-connectors were able to start.
> A subsequent run of the job passed with no issue.
> ={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}= Test Results URI
> ={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}=
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-results/acceptanceTest/1649316934/]
> ={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}={-}=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1082/test-artifacts/1649316934/acceptancetestfiles-openjdk8-1.15.0-build.1082.tgz]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10225) Make gfsh start commands compatible with JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-10225:
---
Description:
When run on JDK 17, numerous acceptance tests fail because a launched locator
or server requires access to the following packages:
- java.base/sun.nio.ch
- java.management/com.sun.jmx.remote.security
When starting locators and servers, gfsh's {{StartLocatorCommand}} and
{{StartServerCommand}} should export these packages to all unnamed modules.
was:
When run on JDK 17, numerous acceptance tests fail because a launched locator
or server requires access to the following packages:
- java.base/sun.nio.ch
- java.management/com.sun.jmx.remote.security
Gfsh's {{StartLocatorCommand}} and {{StartServerCommand}}
> Make gfsh start commands compatible with JDK 17
> ---
>
> Key: GEODE-10225
> URL: https://issues.apache.org/jira/browse/GEODE-10225
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Dale Emery
>Priority: Major
>
> When run on JDK 17, numerous acceptance tests fail because a launched locator
> or server requires access to the following packages:
> - java.base/sun.nio.ch
> - java.management/com.sun.jmx.remote.security
> When starting locators and servers, gfsh's {{StartLocatorCommand}} and
> {{StartServerCommand}} should export these packages to all unnamed modules.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10225) Make gfsh start commands compatible with JDK 17
Dale Emery created GEODE-10225:
--
Summary: Make gfsh start commands compatible with JDK 17
Key: GEODE-10225
URL: https://issues.apache.org/jira/browse/GEODE-10225
Project: Geode
Issue Type: Improvement
Components: gfsh
Reporter: Dale Emery
When run on JDK 17, numerous acceptance tests fail because a launched locator
or server requires access to the following packages:
- java.base/sun.nio.ch
- java.management/com.sun.jmx.remote.security
Gfsh's {{StartLocatorCommand}} and {{StartServerCommand}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10225) Make gfsh start commands compatible with JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-10225:
--
Assignee: Dale Emery
> Make gfsh start commands compatible with JDK 17
> ---
>
> Key: GEODE-10225
> URL: https://issues.apache.org/jira/browse/GEODE-10225
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: Java17
>
> When run on JDK 17, numerous acceptance tests fail because a launched locator
> or server requires access to the following packages:
> - java.base/sun.nio.ch
> - java.management/com.sun.jmx.remote.security
> When starting locators and servers, gfsh's {{StartLocatorCommand}} and
> {{StartServerCommand}} should export these packages to all unnamed modules.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10225) Make gfsh start commands compatible with JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-10225:
---
Labels: Java17 (was: )
> Make gfsh start commands compatible with JDK 17
> ---
>
> Key: GEODE-10225
> URL: https://issues.apache.org/jira/browse/GEODE-10225
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Dale Emery
>Priority: Major
> Labels: Java17
>
> When run on JDK 17, numerous acceptance tests fail because a launched locator
> or server requires access to the following packages:
> - java.base/sun.nio.ch
> - java.management/com.sun.jmx.remote.security
> When starting locators and servers, gfsh's {{StartLocatorCommand}} and
> {{StartServerCommand}} should export these packages to all unnamed modules.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10225) Make gfsh start commands compatible with JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-10225:
---
Affects Version/s: 1.15.0
> Make gfsh start commands compatible with JDK 17
> ---
>
> Key: GEODE-10225
> URL: https://issues.apache.org/jira/browse/GEODE-10225
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Priority: Major
> Labels: Java17
>
> When run on JDK 17, numerous acceptance tests fail because a launched locator
> or server requires access to the following packages:
> - java.base/sun.nio.ch
> - java.management/com.sun.jmx.remote.security
> When starting locators and servers, gfsh's {{StartLocatorCommand}} and
> {{StartServerCommand}} should export these packages to all unnamed modules.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10225) Make gfsh start commands compatible with JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10225:
---
Labels: Java17 pull-request-available (was: Java17)
> Make gfsh start commands compatible with JDK 17
> ---
>
> Key: GEODE-10225
> URL: https://issues.apache.org/jira/browse/GEODE-10225
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: Java17, pull-request-available
>
> When run on JDK 17, numerous acceptance tests fail because a launched locator
> or server requires access to the following packages:
> - java.base/sun.nio.ch
> - java.management/com.sun.jmx.remote.security
> When starting locators and servers, gfsh's {{StartLocatorCommand}} and
> {{StartServerCommand}} should export these packages to all unnamed modules.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8228) CI Failure: SerialWANStatsDUnitTest > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions
[ https://issues.apache.org/jira/browse/GEODE-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett updated GEODE-8228: - Affects Version/s: 1.14.0 > CI Failure: SerialWANStatsDUnitTest > > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions > --- > > Key: GEODE-8228 > URL: https://issues.apache.org/jira/browse/GEODE-8228 > Project: Geode > Issue Type: Test > Components: ci, wan >Affects Versions: 1.14.0 >Reporter: Ernest Burghardt >Priority: Major > Labels: caching-applications > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/247#A] > > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-results/distributedTest/1591318846/ > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > Test report artifacts from this job are available at: > > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-artifacts/1591318846/distributedtestfiles-OpenJDK8-1.14.0-build.0115.tgz -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-8228) CI Failure: SerialWANStatsDUnitTest > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions
[ https://issues.apache.org/jira/browse/GEODE-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett reassigned GEODE-8228: Assignee: Jacob Barrett > CI Failure: SerialWANStatsDUnitTest > > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions > --- > > Key: GEODE-8228 > URL: https://issues.apache.org/jira/browse/GEODE-8228 > Project: Geode > Issue Type: Test > Components: ci, wan >Affects Versions: 1.14.0 >Reporter: Ernest Burghardt >Assignee: Jacob Barrett >Priority: Major > Labels: caching-applications > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/247#A] > > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-results/distributedTest/1591318846/ > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > Test report artifacts from this job are available at: > > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-artifacts/1591318846/distributedtestfiles-OpenJDK8-1.14.0-build.0115.tgz -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-6903) CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion
[
https://issues.apache.org/jira/browse/GEODE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519330#comment-17519330
]
Geode Integration commented on GEODE-6903:
--
Seen in [windows-core-integration-test-openjdk8
#279|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-core-integration-test-openjdk8/builds/279]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1085/test-results/integrationTest/1649378481/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1085/test-artifacts/1649378481/windows-coreintegrationtestfiles-openjdk8-1.15.0-build.1085.tgz].
> CI Failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection
> failed with Assertion
>
>
> Key: GEODE-6903
> URL: https://issues.apache.org/jira/browse/GEODE-6903
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.14.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: flaky
>
> {noformat}
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingGetConnection FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[2]>
> at sun.reflect.GeneratedConstructorAccessor26.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection(GemFireTransactionDataSourceIntegrationTest.java:141)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-results/integrationTest/1561170841/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-artifacts/1561170841/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0399.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8228) CI Failure: SerialWANStatsDUnitTest > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions
[ https://issues.apache.org/jira/browse/GEODE-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-8228: -- Labels: caching-applications pull-request-available (was: caching-applications) > CI Failure: SerialWANStatsDUnitTest > > testReplicatedSerialPropagationWithGroupTransactionEventsSendsBatchesWithCompleteTransactions > --- > > Key: GEODE-8228 > URL: https://issues.apache.org/jira/browse/GEODE-8228 > Project: Geode > Issue Type: Test > Components: ci, wan >Affects Versions: 1.14.0 >Reporter: Ernest Burghardt >Assignee: Jacob Barrett >Priority: Major > Labels: caching-applications, pull-request-available > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/247#A] > > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-results/distributedTest/1591318846/ > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > Test report artifacts from this job are available at: > > > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0115/test-artifacts/1591318846/distributedtestfiles-OpenJDK8-1.14.0-build.0115.tgz -- This message was sent by Atlassian Jira (v8.20.1#820001)
