2 Replies Latest reply on Jun 16, 2008 9:57 PM by starksm64

    VFS errors

    starksm64

      In the current vfs trunk I'm seeing 13 test failures:

      [515][valkyrie: trunk]$ mvn test
      [INFO] Scanning for projects...
      WAGON_VERSION: 1.0-beta-2
      [INFO] ------------------------------------------------------------------------
      [INFO] Building JBoss VFS
      [INFO] task-segment: [test]
      [INFO] ------------------------------------------------------------------------
      ...
      -------------------------------------------------------
       T E S T S
      -------------------------------------------------------
      Running org.jboss.test.virtual.test.ExplodeTestCase
      Tests run: 5, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.149 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.JAREntryTestCase
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.103 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.TempTestCase
      Tests run: 5, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.195 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.CopyJAREntryTestCase
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.093 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.UnpackTestCase
      Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.145 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.CopyJARCacheUnitTestCase
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.094 sec <<< FAILURE!
      Running org.jboss.test.virtual.test.JARCacheUnitTestCase
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.1 sec <<< FAILURE!
      
      Results :
      
      Tests in error:
      
      Tests run: 531, Failures: 0, Errors: 13, Skipped: 0
      


      The CopyTest assertions about a directory size being 0 are just wrong, I'm not sure what this is supposed to be checking?
      junit.framework.AssertionFailedError: expected:<0> but was:<102>
       at junit.framework.Assert.fail(Assert.java:47)
       at junit.framework.Assert.failNotEquals(Assert.java:282)
       at junit.framework.Assert.assertEquals(Assert.java:64)
       at junit.framework.Assert.assertEquals(Assert.java:136)
       at junit.framework.Assert.assertEquals(Assert.java:142)
       at org.jboss.test.virtual.test.CopyTest.assertReplacement(CopyTest.java:184)
       at org.jboss.test.virtual.test.CopyTest.assertReplacement(CopyTest.java:173)
       at org.jboss.test.virtual.test.CopyTest.assertExplodedReplacement(CopyTest.java:167)
       at org.jboss.test.virtual.test.DetachedCopyTest.assertNestedLevel(DetachedCopyTest.java:58)
       at org.jboss.test.virtual.test.CopyTest.testUnpackDeepLevel(CopyTest.java:142)
      



        • 1. Re: VFS errors
          starksm64

          The TempTestCase failures are the same issue. The directory size comparison is a file system/os specific check that really should just be skipped. Its not a meaningful value.

          • 2. Re: VFS errors
            starksm64

            I dropped the directory file size check from CopyTest and this leaves these 4 errors:

            Running org.jboss.test.virtual.test.JAREntryTestCase
            Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.095 sec <<< FAILURE!
            Running org.jboss.test.virtual.test.CopyJAREntryTestCase
            Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.094 sec <<< FAILURE!
            Running org.jboss.test.virtual.test.CopyJARCacheUnitTestCase
            Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.096 sec <<< FAILURE!
            Running org.jboss.test.virtual.test.JARCacheUnitTestCase
            Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.096 sec <<< FAILURE!
            

            which look related to JBVFS-7.