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] [Updated] (DERBY-6064) Failures in upgradeTests.Changes10_9 related to index cardinality statistics
Date Sun, 03 Feb 2013 15:00:15 GMT

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

Kristian Waagan updated DERBY-6064:
-----------------------------------

    Issue & fix info:   (was: Patch Available)
       Fix Version/s: 10.10.0.0
             Summary: Failures in upgradeTests.Changes10_9 related to index cardinality statistics
 (was: Failures in upgradeTests.changes10_9 related to index cardinality statistics)

Thanks, Dag.
I'll update the comment to make it more accurate.
Committed patch 1a to trunk with revision 1441923.

I'll also look at merging the fix into the 10.9-branch.
                
> 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
>             Fix For: 10.10.0.0
>
>         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