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 Fri, 01 Feb 2013 12:06:12 GMT

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

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

    Attachment: derby-6064-1a-istat_upgrade_test_fixes.diff

Attaching patch 1a, which is a suggestion on how to fix the problem.

The test helper class DisposableIndexStatistics now adjusts  the expected counts for statistics
entries based on the version of the old database. Versions with the fix for DERBY-5681 will
have one less entry. The range check I introduced for the overall number of statistics entries
is a bit fuzzy, but I think it's good enough - especially since the tests would fail in other
places if we made old versions stop generating statistics for single column unique indexes.

Patch ready for review.
                
> 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