Derby
  1. Derby
  2. DERBY-2636

ImportExportProcedureTestjunit.framework.AssertionFailedError encountered running full junit test suite

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 10.3.1.4
    • Fix Version/s: None
    • Component/s: Test
    • Labels:
      None
    • Environment:
    • Bug behavior facts:
      Regression Test Failure

      Description

      Encountered the following error when running the full junit test suite:

      2) ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.da
      t
      at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSet
      up.java:129)
      at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSe
      tup.java:38)
      at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.j
      ava:104)
      at java.security.AccessController.doPrivileged(AccessController.java:193)
      at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatab
      aseSetup.java:101)
      at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetu
      p.java:127)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:23)

      1. derby.log
        2.27 MB
        Mike Matrigali

        Issue Links

          Activity

          Hide
          Mike Matrigali added a comment -

          Here is the derby.log from the full suite, I couldn't match up the error with anything in the log - If anyone knows how please post the info.

          Show
          Mike Matrigali added a comment - Here is the derby.log from the full suite, I couldn't match up the error with anything in the log - If anyone knows how please post the info.
          Hide
          Julius Stroffek added a comment -

          The above exception is thrown when DropDatabaseSetup is not able to delete the file 'extinout\t1.dat'.

          I observed similar problem some time ago when I ran junit tests on NFS file system. When I ran tests it failed on the assertion testing the delete of an empty directory (at DropDatabaseSetup.java:134). When I had a look to the directory I found a file named '.nfsXXXX' there. I discussed this with some NFS guys and discovered that when NFS is going to delete the file that is already opened it will rename the file to '.nfsXXXX' and keep it in the same directory.

          When you use POSIX compliant file system (NFS is not POSIX compliant, I had no idea about FAT and NTFS) and you are trying to delete a file that is already opened, the file will be deleted from the directory and also the handle will still remain valid. Once you close the handle the file will get deleted from the disk.

          Do you have NTFS or FAT32 filesystem? What happens when you try to delete an open file? I believe it will fail.

          I think that ImportExportProcedureTest would probably keep the file 'extinout\t1.dat' open for some reason.

          Show
          Julius Stroffek added a comment - The above exception is thrown when DropDatabaseSetup is not able to delete the file 'extinout\t1.dat'. I observed similar problem some time ago when I ran junit tests on NFS file system. When I ran tests it failed on the assertion testing the delete of an empty directory (at DropDatabaseSetup.java:134). When I had a look to the directory I found a file named '.nfsXXXX' there. I discussed this with some NFS guys and discovered that when NFS is going to delete the file that is already opened it will rename the file to '.nfsXXXX' and keep it in the same directory. When you use POSIX compliant file system (NFS is not POSIX compliant, I had no idea about FAT and NTFS) and you are trying to delete a file that is already opened, the file will be deleted from the directory and also the handle will still remain valid. Once you close the handle the file will get deleted from the disk. Do you have NTFS or FAT32 filesystem? What happens when you try to delete an open file? I believe it will fail. I think that ImportExportProcedureTest would probably keep the file 'extinout\t1.dat' open for some reason.
          Hide
          Mike Matrigali added a comment -

          I see this on windows XP laptop with no external files. I believe the filesystem is ntfs.

          Show
          Mike Matrigali added a comment - I see this on windows XP laptop with no external files. I believe the filesystem is ntfs.
          Hide
          Mike Matrigali added a comment -

          Also failed on windows 2003, 64 bit edition, ibm 142 jvm against 10.3 1st release candidate:

          There was 1 failure:
          1) ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat
          at java.lang.Throwable.<init>(Throwable.java:58)
          at java.lang.Throwable.<init>(Throwable.java:72)
          at junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:129)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:38)
          at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:104)
          at java.security.AccessController.doPrivileged(AccessController.java:187)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:101)
          at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:127)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
          at junit.extensions.TestSetup.run(TestSetup.java:23)

          Show
          Mike Matrigali added a comment - Also failed on windows 2003, 64 bit edition, ibm 142 jvm against 10.3 1st release candidate: There was 1 failure: 1) ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat at java.lang.Throwable.<init>(Throwable.java:58) at java.lang.Throwable.<init>(Throwable.java:72) at junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:129) at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:38) at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:104) at java.security.AccessController.doPrivileged(AccessController.java:187) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:101) at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:127) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:23)
          Hide
          Ramandeep Kaur added a comment -

          Also failed on Windows 2000 for ibm142 and ibm15 for 10.3 beta candidate.
          1) ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:129)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:38)
          at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:104)
          at java.security.AccessController.doPrivileged(AccessController.java:193)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:101)
          at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:127)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
          at junit.extensions.TestSetup.run(TestSetup.java:23)

          Show
          Ramandeep Kaur added a comment - Also failed on Windows 2000 for ibm142 and ibm15 for 10.3 beta candidate. 1) ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:129) at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:38) at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:104) at java.security.AccessController.doPrivileged(AccessController.java:193) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:101) at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:127) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:23)
          Hide
          Mamta A. Satoor added a comment -

          Is this error "ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat" intermittent? And have they occuring intermittently on 10.3 codeline only?

          I recently ran org.apache.derbyTesting.functionTests.suites.All on both 10.3 and trunk codeline and did not run into this failure on either one of the 2 codelines.

          Show
          Mamta A. Satoor added a comment - Is this error "ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat" intermittent? And have they occuring intermittently on 10.3 codeline only? I recently ran org.apache.derbyTesting.functionTests.suites.All on both 10.3 and trunk codeline and did not run into this failure on either one of the 2 codelines.
          Hide
          Kathey Marsden added a comment -

          Mamta asked;

          >Is this error >"ImportExportProcedureTestjunit.framework.AssertionFailedError: >extinout\t1.dat" intermittent? And have they occuring intermittently on 10.3 >codeline only?

          I see these fairly frequently but not always on both trunk and 10.3 with IBM 1.4.2 and IBM 1.5 jvm's on Windows XP.

          Show
          Kathey Marsden added a comment - Mamta asked; >Is this error >"ImportExportProcedureTestjunit.framework.AssertionFailedError: >extinout\t1.dat" intermittent? And have they occuring intermittently on 10.3 >codeline only? I see these fairly frequently but not always on both trunk and 10.3 with IBM 1.4.2 and IBM 1.5 jvm's on Windows XP.
          Hide
          Mike Matrigali added a comment -

          I also see this frequently, but not always when running on 10.3 and trunk on windows XP using ibm15 jvm. I run against classes rather than jars, so this happens both with classes and jar test running. Again I have been running the full junit test suite on a single processor laptop.

          Show
          Mike Matrigali added a comment - I also see this frequently, but not always when running on 10.3 and trunk on windows XP using ibm15 jvm. I run against classes rather than jars, so this happens both with classes and jar test running. Again I have been running the full junit test suite on a single processor laptop.
          Hide
          Myrna van Lunteren added a comment -

          DERBY-3068 and this appear to be manifestations of the same issue.

          Show
          Myrna van Lunteren added a comment - DERBY-3068 and this appear to be manifestations of the same issue.
          Hide
          Myrna van Lunteren added a comment -

          The fix for DERBY-3068 appears to also have resolved this issue.

          Show
          Myrna van Lunteren added a comment - The fix for DERBY-3068 appears to also have resolved this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mike Matrigali
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development