db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-937) Instability in wisconsin test
Date Tue, 07 Mar 2006 00:33:29 GMT
    [ http://issues.apache.org/jira/browse/DERBY-937?page=comments#action_12369112 ] 

A B commented on DERBY-937:

I noticed that the wisconsin test attempts to run with the "noTimeout" property set to true,
 but in the wisconsin_derby.properties file, there's actually a typo:


There is an "r" missing after the word "optimize"; i.e. the property should be:


While I am still unable to reproduce the diff on my own machine, and while the Tinderbox tests
on most platforms do _not_ show the diff you posted, it's nonetheless possible that for different
machines the optimizer is timing out at different times, causing the diff.

With that in mind I corrected the typo locally and re-ran the test; when I did so, it still
passed for me.  So if possible could you (or anyone else seeing this diff) correct the typo
in wisconsin_derby.properties file and then run again to see if the test still fails?

March 3rd was the day my optimizer changes for DERBY-805 went into the codeline, so if the
test has been failing consistently for you since then, and if fixing the properties typo doesn't
help, then I'll have to look more closely at this to see what role my DERBY-805 changes might
have here...


> Instability in wisconsin test
> -----------------------------
>          Key: DERBY-937
>          URL: http://issues.apache.org/jira/browse/DERBY-937
>      Project: Derby
>         Type: Test
>   Components: Regression Test Failure, Test
>     Reporter: Rick Hillegas

> 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