[
https://issues.apache.org/jira/browse/DERBY-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702426#action_12702426
]
Kathey Marsden commented on DERBY-4168:
---------------------------------------
Ah, I see, this was actually user error. I see the size on my problematic
derbyTesting.jar matches RC1, when I transferred the new files over I must have
neglected to cd over to the test directory and transfer derbyTesting.jar over.
I should have cleared the jars out from my RC1 run to avoid the possibility
for such a mistake. Sorry to waste everyone's time.
>
> testMkdirsInvalidAbsolute(org.apache.derbyTesting.unitTests.junit.VirtualFileTest)junit.framework.AssertionFailedError
> on Zos
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4168
> URL: https://issues.apache.org/jira/browse/DERBY-4168
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.5.1.1
> Environment: Zos IBM 1.6 pmz3160sr2ifx-20081021_01
> Reporter: Kathey Marsden
> Priority: Minor
>
> On Zos with 10.5.1.1 (RC2) and IBM 1.6 pmz3160sr2ifx-20081021_01 I saw this
> failure. I did not see it with RC1 with the 64bit jvm.
> 1)
> testMkdirsInvalidAbsolute(org.apache.derbyTesting.unitTests.junit.VirtualFileTest)junit.framework.AssertionFailedErro
> r
> at
> org.apache.derbyTesting.unitTests.junit.VirtualFileTest.testMkdirsInvalidAbsolute(VirtualFileTest.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
