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-4833) Prepare existing JUnit tests for running with automatic index statistics generation
Date Thu, 16 Dec 2010 13:35:11 GMT

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

Kristian Waagan commented on DERBY-4833:
----------------------------------------

Yes, this can happen in all tests that query the lock table, but there are various prerequisites
that must be met before the automatic index statistics updates kick in (these may change with
the implementation/tuning).
A quick find/grep resulted in something like 22 hits (on the file level) in the tests directory,
and 24 in the masters directory.

I have run both suites.All and derbyall numerours times without having seen other problems,
but that may change on other machines and operating systems.
If we address this up-front, I would lean towards adding a way to wait for the updates to
finish to potentially get more test coverage for the feature, but disabling it would also
work fine.

I don't have any strong feelings about this right now, and more importantly, I don't have
much time to work on it now...
If people start seeing intermittent failures when the feature has been committed, it would
probably be best to address all affected tests in one go.

> Prepare existing JUnit tests for running with automatic index statistics generation
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-4833
>                 URL: https://issues.apache.org/jira/browse/DERBY-4833
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.7.1.1
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-4833-1a-orderbyandsortavoidancetest_adjustment.diff, derby-4833-2a-updatelocks_disable_autostats.diff
>
>
> During prototyping of a mechanism to create and update index statistics automatically
(see DERBY-4771) it turned out that some of the tests fail due to the presence of [improved]
index statistics.
> Where appropriate the tests should be adjusted to cope with this background activity,
and where not appropriate it should be noted such that the feature, when introduced, can be
disabled.
> As part of this effort I will introduce a utility class for dealing with index statistics
in tests. These will be used by some existing tests and also the new tests that will be written
for the new feature.
> At this point two tests requiring adjustments have been identified (OrderByAndSortAvoidance,
UpdateStatisticsTest), and one is under investigation (AutoIncrementTest). More may surface
as the work on the feature progress.

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


Mime
View raw message