db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Wed, 25 Feb 2009 17:41:02 GMT

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

Kristian Waagan commented on DERBY-646:

Here are some results from running 'ant junitreport' with patch 2a

The prefix 'org.apache.derbyTesting.' has been removed for brevity.
The first number is the number of tests run with the vfmem back end,
the second number is the number of tests run with a clean trunk.
Note that I changes the memory back end to be the default back end in
this run (modified the entry for DIRECTORY storage factory in BaseMonitor), and
I also changed DropDatabaseSetup to delete the in-memory database.

Suites run without failures:
junit.EnvTest (9/9)
functionTests.tests.jdbcapi.AutoloadTest (3/3)
functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest (8/8)
functionTests.tests.jdbcapi.JDBCDriversClientTest (4/4)
functionTests.tests.jdbcapi.JDBCDriversAllTest (12/12)
functionTests.tests.tools._Suite (87/87)
functionTests.tests.demo._Suite (2/2)
functionTests.tests.engine._Suite (11/11)
functionTests.suites.EncryptionSuite (7/7)
functionTests.tests.jdbc4._Suite (896/898) // One test added later
functionTests.tests.management._Suite (100/100)

The follwing tests had failures and/or errors:
functionTests.tests.derbynet._Suite (t=122/f=1/e=0)
    (f) ShutDownDBWhenNSShutsDownTest.testDatabasesShutDownWhenNSShutdown
functionTests.tests.lang._Suite (t=1473/f=4/e=2)
    (f) DatabaseClassLoadingTest.testCreateDatabaseJar
    (f) DatabaseClassLoadingTest.testDatabaseInJar
    (f) ConnectTest.testDBName
    (f) ConnectTest.testDBName
    (e) DatabaseClassLoadingTest.testHackedJarReplacedClass
    (e) DBInJarTest.testConnectDBInJar
functionTests.tests.jdbcapi._Suite (t=6301/f=2/e=0)
    (f) PoolXADSCreateShutdownDBTest.testXADS
    (f) PoolXADSCreateShutdownDBTest.testXADS
functionTests.tests.store._Suite (t=98/f=4/e=19)
    (f) BootAllTest.testSettingBootAllPropertyWithHomePropertySet
    (f) OSReadOnlyTest.testOSReadOnly
    (f) OSReadOnlyTest.testOSReadOnly
    (f) BackupRestoreTest.testDerby3875
        o Ok, test is trying to correct file on disk.
    (e) OfflineBackupTest.testCreateFromRestoreFrom
 6x (e) EncryptionKeyAESTest
 6x (e) EncryptionKeyBlowfishTest
 6x (e) EncryptionKeyDESTest
    (crashes due to ant/junit problem, will rerun later)
    (e) AccessControlException
functionTests.tests.upgradeTests._Suite (t=420/f=12/e=42)
    (needs investigation)
        o Ok, fails because it sets the heap size really low and tries
          to insert data that is bigger than the heap.
To sum up, I'm currently getting 23 failures and 65 errors.
The time it takes to run the suites is around 45 minutes.
I believe the 'ant junitreport' target is roughly equal to running

> In-memory backend storage support
> ---------------------------------
>                 Key: DERBY-646
>                 URL: https://issues.apache.org/jira/browse/DERBY-646
>             Project: Derby
>          Issue Type: New Feature
>          Components: Store
>         Environment: All
>            Reporter: Stephen Fitch
>         Attachments: derby-646-1a-raw-compiles.diff, derby-646-1a-raw-compiles.stat,
derby-646-20090222.diff, derby-646-20090222.stat, derby-646-2a-vfmem_first_rev.diff, derby-646-2a-vfmem_first_rev.stat,
derby-646-performance_comparison_1a.txt, svn.diff
> To allow creation and modification of databases in-memory without requiring disk access
or space to store the database.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message