db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4168) testMkdirsInvalidAbsolute(org.apache.derbyTesting.unitTests.junit.VirtualFileTest)junit.framework.AssertionFailedError on Zos
Date Fri, 24 Apr 2009 00:29:30 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702174#action_12702174

Kathey Marsden commented on DERBY-4168:

I put some printlns in the code and am seeing some pretty strange behavior.
I copied the relevant source to the z/OS machine so I could make changes and compile there.
I copied the files under org/apache/derby/impl/io/vfmem and necessary supporting files.  
My CLASSPATH contains ., junit.jar and derbyTesting.jar from RC2.  The very strange thing
is that if I copy VirtualFileTest.java to the z/OS machine and use the locally compiled copy,
test passes and the problem does not reproduce, but pointing to the RC2 derbyTesting.jar I

can make the problem happen.

I have printlns in DataStore on entry to createEntry right after npath is determined, when
a parent is added to parents, 
and when a lookup for a parent is not in files.

Here is the output I see when the test passes (test built locally on z/OS).

testMkdirsInvalidAbsolute createEntry: iPath=/ nPath=/
createEntry: iPath=/directory nPath=/directory
Adding parent /
createEntry: iPath=/directory/afile nPath=/directory/afile
Adding parent /directory
Adding parent /
[snip other irrelevant output]
used 22 ms .

and when it fails, pointing to derbyTesting.jar
testMkdirsInvalidAbsolute createEntry: iPath=/directory nPath=/directory
Adding parent /
Entry for parent:/is not in files
used 32 ms F.

In the failing case we never see a createEntry for /, but the test clearly and unconditionally

calls store.createEntry(java.io.File.separator, true) in getStore()

Tomorrow I will try to rebuild the testing jar with some printlns and see what is going on.
I tried to run with -Xint to make sure it is not a JIT issue.

>  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:
>         Environment: Zos IBM 1.6 pmz3160sr2ifx-20081021_01
>            Reporter: Kathey Marsden
>            Priority: Minor
> On Zos with (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.

View raw message