You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2022/06/08 16:51:00 UTC
[jira] [Assigned] (GEODE-10364) DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions
[ https://issues.apache.org/jira/browse/GEODE-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jinmei Liao reassigned GEODE-10364:
-----------------------------------
Assignee: Jinmei Liao
> DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions
> ------------------------------------------------------------------------------------------
>
> Key: GEODE-10364
> URL: https://issues.apache.org/jira/browse/GEODE-10364
> Project: Geode
> Issue Type: Bug
> Components: management, rest (admin), tests
> Affects Versions: 1.15.0
> Reporter: Udo Kohlmeyer
> Assignee: Jinmei Liao
> Priority: Minor
> Labels: blocks-1.16.0
>
> DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions is failing with unexpected log entries.
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2671
> {code:java}
> DeploymentManagementRedployDUnitTest > hotDeployShouldNotResultInAnyFailedFunctionExecutions FAILED
> 01:44:15 java.lang.AssertionError: Suspicious strings were written to the log during this run.
> 01:44:15 Fix the strings or use IgnoredException.addIgnoredException to ignore.
> 01:44:15 -----------------------------------------------------------------------
> 01:44:15 Found suspect string in 'dunit_suspect-vm0.log' at line 531
> 01:44:15
> 01:44:15 PK????????{}?T????????????)???DeployCommandRedeployDUnitFunctionA.class???????n?@??????IhChh?????:??Bp+B??E EP5P$n??J?r?h?F?g???P9??<?b?qUp?H???w??y????????O???<??Q/b??y?-b?????1P7p??}?????????C?l?3d:??3,???_??!????K;?1W/F??f??j??-????@I???(O?0???a??k?J????<8?????N?H?????????s??1?_ZN??#V/??%|??{???(?????x??**??C??*1??y??o?????<o3??Ue??Lm???J???????????S??@???FG|?}v?P3?%???P?E??v??
> 01:44:15 ??`?????2??G??%????%?????^
> 01:44:15 O?C
> 01:44:15 ??i?????.w?Y???????M??y;???K????????dl??8????u1???OZB#??k?-Na????y0=??7??N+?5?????^??)???*Er:F?c4]I}N?+?o???5zR?H?i?[X??&A?[l?#?P??#??eN!:? v?v??????u?2?????W?r?$?Kqu??YnS??+V}E.???j-?{?7PK??4|'?????=???PK??????????{}?T4|'?????=???)?????????????????DeployCommandRedeployDUnitFunctionA.class????PK??????????[???j?????
> 01:44:15 --cvFOdAqPh74YsEftzj4GE_lSmdgeMggm6mUZS8E
> 01:44:15 Content-Disposition: form-data; name="config"
> 01:44:15 Content-Type: application/json
> 01:44:15
> 01:44:15 -----------------------------------------------------------------------
> 01:44:15 Found suspect string in 'dunit_suspect-vm0.log' at line 550
> 01:44:15
> 01:44:15 PK????????{}?T????????????)???DeployCommandRedeployDUnitFunctionA.class???????n?@??????IhChh?????:???p+B??E EP5P$n??J?r?h?F?g???P9??<?b?qUp?H???w??y????????O???<??Q/b??y?-b?????1P7p??}?????????C?l?3d:??3,???_??!????K;?1W/F??f??j??-????@I???(O?0???a??k?J????<8?????N?H?????????s??1?_ZN??#V/??%|??{???(?????x??**??C??*1??y??o?????<o3??Ue??Lm???J???????????S??@???FG|?}v?P3?%???P?E??v??
> 01:44:15 ??`?????2??G??%????%?????^
> 01:44:15 O?C
> 01:44:15 ??i?????.w?Y???????M??y;???K????????dl??8????u1???OZB#??k?-Na????y0=??7??N+?5?????^??)???*Er:F?c4]I}N?+?o???5zR?H?i?[X??&A?[l?#?P??#??eN!:? v?v??????u?2?????W?r?$?Kqu??YnS??+V}E.???j-?{?7PK??????????=???PK??????????{}?T????????=???)?????????????????DeployCommandRedeployDUnitFunctionA.class????PK??????????[???j?????
> 01:44:15 ---UjSGLHVgaMcjtjM7IJfWJ3fPZEhjOGN
> 01:44:15 Content-Disposition: form-data; name="config"
> 01:44:15 Content-Type: application/json {code}
> In order to resolve this issue the ManagementLoggingFilter needs to be a little more discriminant on what it logs out, as it currently is serializing the jar file contents as a String, which is causing this issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)