[
https://issues.apache.org/jira/browse/DERBY-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113102#comment-13113102
]
Dag H. Wanvik commented on DERBY-5420:
--------------------------------------
Just to clearify, the bug is not really intermittent after all, it just
appeared that way, since depending on which tests ahead of TableLockBasicTest I
commented out, the first setting of the decimal format above might happen in a
test running with a specific English locale, or in a test running with the
default one.
For example, AccessTest calls SYSCS_GET_RUNTIMESTATISTICS without setting
explicit locale, but this test uses the RuntimeStatisticsParser and doesn't
worry about the double number estimated row count, so AccessTest test is not
impacted by (an unexpected form of) decimal printing.
> TableLockBasicTest is locale sensitive: failed with Norwegian locale on
> Windows.
> --------------------------------------------------------------------------------
>
> Key: DERBY-5420
> URL: https://issues.apache.org/jira/browse/DERBY-5420
> Project: Derby
> Issue Type: Bug
> Components: Test
> Environment: Windows Vista SP2, Norwegian locale, JDK 7.
> Reporter: Dag H. Wanvik
> Priority: Minor
>
> The execution plans are asserted in this test and I saw this diff:
> Expected:
> :
> optimizer estimated row count: 6.00
> optimizer estimated cost: 100.40<
> Found:
> :
> optimizer estimated row count: 6,00
> optimizer estimated cost: 100,40<
> the latter using a decimal comma whereas a decimal point is expected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
