You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (Jira)" <ji...@apache.org> on 2021/09/14 16:50:00 UTC

[jira] [Updated] (GEODE-9595) Analyze serializables testSerializables fails with FileSystemNotFoundException

     [ https://issues.apache.org/jira/browse/GEODE-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund updated GEODE-9595:
-----------------------------
    Summary: Analyze serializables testSerializables fails with FileSystemNotFoundException  (was: Analyze serializables integration tests fail with ZipException)

> Analyze serializables testSerializables fails with FileSystemNotFoundException
> ------------------------------------------------------------------------------
>
>                 Key: GEODE-9595
>                 URL: https://issues.apache.org/jira/browse/GEODE-9595
>             Project: Geode
>          Issue Type: Bug
>          Components: build
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>              Labels: pull-request-available
>
> I found circular dependencies that cause failures in new tests in geode-core, geode-cq, geode-gfsh, geode-management, geode-wan, geode-web-api.
> The circular dependencies result in the module such as geode-core adding geode-core*.jar to the classpath of the tests. Classes and resources are then loaded into the test JVM from the .jar file instead of from the filesystem. This causes issues only in some tests such as AnalyzeSerializables integration tests.
> To reproduce:
> 1) Delete any line from geode-core/src/main/resources/org/apache/geode/internal/sanctioned-geode-core-serializables.txt
> 2) Execute $ ./gradlew geode-core:integrationTest --tests AnalyzeCoreSerializablesIntegrationTest



--
This message was sent by Atlassian Jira
(v8.3.4#803005)