db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6064) Failures in upgradeTests.changes10_9 related to index cardinality statistics
Date Sat, 02 Feb 2013 06:38:15 GMT

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

Dag H. Wanvik commented on DERBY-6064:
--------------------------------------

Patch looks good. One comment threw me off a bit:

                // We expect that the maximum number of statistics have been
                // created here, since we're using an older version of Derby
                // that contained a bug and lacked the latest optimizations.

with "older version" being 10.8.3 the bug is gone, right? If so the comment isn't entirely
accurate and it woould be good to fix that.


                
> Failures in upgradeTests.changes10_9 related to index cardinality statistics
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-6064
>                 URL: https://issues.apache.org/jira/browse/DERBY-6064
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.1.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-6064-1a-istat_upgrade_test_fixes.diff
>
>
> The upgrade test fails when run with 10.8.3. The reason is that a fix has been backported
to 10.8.3, and older branches back to 10.3, and this fix invalidates assumptions made in some
of the tests in Changes10_9.
> Example of failures:
> https://builds.apache.org/job/Derby-10.9-suites.All/60/testReport/
> As a side note, I'm wondering if we don't have good enough routines to make sure we run
the upgrade tests with maintenance releases on older branches before releasing them. I don't
know if we can avoid this situation in general, that would at least require very careful consideration
on how to write the upgrade test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message