You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/10 17:36:31 UTC
[jira] Updated: (DERBY-3771) testClasspathChecker under
SysinfoCPCheckTest failed on Zos
[ https://issues.apache.org/jira/browse/DERBY-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3771:
----------------------------------
Attachment: derby-3771_diff.txt
Attached is a patch for this issue. Removed the US-ASCII encoding for the print stream and used the default encoding.
The only thing I wonder about is if there was put in there intentionally for some reason.
> testClasspathChecker under SysinfoCPCheckTest failed on Zos
> ------------------------------------------------------------
>
> Key: DERBY-3771
> URL: https://issues.apache.org/jira/browse/DERBY-3771
> Project: Derby
> Issue Type: Bug
> Components: Test
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: derby-3771_diff.txt
>
>
> estClassPathChecker(org.apache.derbyTesting.functionTests.tests
> .tools.SysinfoCPCheckTest)junit.framework.ComparisonFailure:
> expected:<Testing for presence of all Derby-related
> libraries; typically, only some are needed.> but
> was:<???????@???@????????@??@???@?????`???????@?????????^@???
> ??????k@????@????@???@??????K???@?@????@??@????????@?????????k@
> ????@????@???K??????K?????K?????K???????@`??@?????????@??@?????
> @????z@@@?????@????????@??????@???????@M?????K???]@@@??????@?
> ?@??????@??????????@??????@??@????@??????@???@?????@???K??????K?
> ????K????????K????????z@??????@??????@M????K????K???????????????
> ??@???????????????????]@@@?????@????????@??????@???????@M????
> ?K???]@@@??????@??@??????@??????????@??????@??@????@??????@???@
> ?????@???K??????K?????K????????K????????z@??????@??????@M????K??
> ??K?????????????????@???????????????????]@@@?????@???????@???
> ???@???????@M????????K???]@@@??????@??@??????@??????????@??????
> @??@????@??????@???@?????@???K??????K?????K????K????????????????
> ????z@??????@??????@M????K????K?????????????????@???????????????
> ????]@@@?????@??????@?????????@M???????????K???]@@@??????@??
> @??????@??????????@??????@??@????@??????@???@?????@???K??????K??
> ???K????K????????????z@??????@??????@M????K????K????????????????
> ?@???????????????????]@@@?????@?????@???????@M??????????K???]
> @@@??????@??@??????@??????????@??????@??@????@??????@???@?????@
> ???K??????K?????K?????K??z@??????@??????@M????K????K????????????
> ?????@???????????????????]???@?????@??@?????@????z@@@?????
> @??????@?????????@M??????K???]@@@@M???K???K???K???K?????????@??
> ?@?????K]>
> at
> org.apache.derbyTesting.functionTests.tests.tools.SysinfoCPCheck
> Test.testClassPathChecker(SysinfoCPCheckTest.java:162)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
> Impl.java:59)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
> AccessorImpl.java:39)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.
> java:101)
> I was able to reproduce this on windows with the sun 1.5 or 1.6 jvm by running with
> -Dfile.encoding="UTF-16"
>
> At first glance, I think this might be a test issue.
> The test sets
> final String outputEncoding = "US-ASCII"; and then
> PrintStream testOut = new
> PrintStream(rawBytes,
> false, outputEncoding);
> setSystemOut(testOut);
> I'm not sure, but I think it should use the default encoding in this case instead of changing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.