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] Resolved: (DERBY-5040) On Windows, cascade of errors after failed test AutomaticIndexStatisticsTest
Date Wed, 02 Mar 2011 20:58:36 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan resolved DERBY-5040.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.8.0.0
         Assignee: Kristian Waagan

The cascade-effect has been fixed by switching from using the default db to a separate db.
The test failure itself is hopefully adressed by DERBY-4915.

I don't expect more work for this issue.

> On Windows, cascade of errors after failed test AutomaticIndexStatisticsTest
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-5040
>                 URL: https://issues.apache.org/jira/browse/DERBY-5040
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.8.0.0
>            Reporter: Dag H. Wanvik
>            Assignee: Kristian Waagan
>              Labels: derby_triage10_8
>             Fix For: 10.8.0.0
>
>         Attachments: derby-5040-1a-use_separate_db.diff
>
>
> Cf log here:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-1070264.html
> Not sure if this is distinct (or not) from other errors we have seen after the enabling
of the statistics auto-refresh patch.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message