db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-937) Instability in wisconsin test
Date Thu, 29 Jun 2006 18:32:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-937?page=all ]

Mike Matrigali updated DERBY-937:

committed change to trunk:

r418108 | mikem | 2006-06-29 11:27:51 -0700 (Thu, 29 Jun 2006) | 16 lines

DERBY-937, committing change by      Andreas Korneliussen.

notes by Andreas:
I was able to reproduce this problem on every run on a very fast laptop (it was
not reproducible on any other Windows lab machine I have tried). This laptop hap
pens to be the same kind as Ole uses for the nightly tests.

Adding a 10 second sleeping period after the population of the tables, did not h
ave any effect. I therefore tried to do run a compress on the tables (based on t
he assumption that statistics is updated on compress), and now the test does not
 fail for me anymore.

Attached is the patch which makes this test stop failing. The patch does not see
m to have any sideeffects on other platforms (Solaris) tested, however the test
will use more time.

note by mike:
I ran this change 20 times and it worked on my laptop, it would always fail
a few times out of 20 before the fix.  I am not sure why this fix works as
the test seems to already create indexes after tables so statistics should
already be up to date.

> 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:
>     Reporter: Rick Hillegas
>     Assignee: Andreas Korneliussen
>      Fix For:
>  Attachments: 10.1_05_05_06_failure.zip, DERBY-937.diff, DERBY-937.stat
> 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:
For more information on JIRA, see:

View raw message