db-derby-dev mailing list archives

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

Andreas Korneliussen updated DERBY-937:

    Attachment: DERBY-937.diff

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 happens 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 have any effect.
I therefore tried to do run a compress on the tables (based on the 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 seem to have
any sideeffects on other platforms (Solaris) tested, however the test will use more time.

> 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
>  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