Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <21728622.1151330851144.JavaMail.jira@brutus>
Date: Mon, 26 Jun 2006 14:07:31 +0000 (GMT+00:00)
From: "Andreas Korneliussen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-937) Instability in wisconsin test
In-Reply-To: <1690588452.1139412931072.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-937?page=comments#action_12417814 ] 

Andreas Korneliussen commented on DERBY-937:
--------------------------------------------

This test is failing pretty consistently on Windows. 

I looked at the properties for the test, and found this:

#checkpoint influences the plans in some cases becuase rows count 
#getupdated on checkpoint, following is necessart to check some plans
derby.storage.checkpointInterval=100000

Based on this, I have the following question:
Does really the checkpointinterval influence this test ? The indexes are created after the tables are populated, so the statistics should be updated or ..?

Would it make any difference to the test if we add a sleeping period after the population of the tables ? I think this could make a difference, if the failures are caused by the optimizer choosing plans based on outdated statistics.

> Instability in wisconsin test
> -----------------------------
>
>          Key: DERBY-937
>          URL: http://issues.apache.org/jira/browse/DERBY-937
>      Project: Derby
>         Type: Test

>   Components: Test, Regression Test Failure
>     Versions: 10.1.2.4
>     Reporter: Rick Hillegas
>  Attachments: 10.1_05_05_06_failure.zip
>
> The lang/wisconsin.java test prints out query plans. These plans differ depending on your platform. When run under cygwin on xp, the plans vary from the canonized results. I am seeing this instability in my own test environment and in the tinderbox tests against cygwin.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira