You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/01/28 21:02:49 UTC
[jira] Closed: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
[ https://issues.apache.org/jira/browse/DERBY-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-804.
------------------------------------
Resolution: Won't Fix
I'm marking this one as won't fix - basically because I don't think anyone intends to (or they would have done so already), and we're dropping support for jdk 1.3.1 based jvms with 10.3. If anyone opposes this decision, they can reopen this.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: https://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.2.1, 10.2.1.6
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat, DERBY-804_10.2_skipcomment.diff
>
>
> For at least half a year (oldest record I could find is 6/18/05), the test lang/floattypes has been failing with jdk131, ibm131 and j9 2.0 (wsdd5.6).
> The failure seems related to a different handling of Decimal values. There are differences between the exact behavior between these 3 jvms also.
> The behavior for jdk131 is like so:
> *** Start: floattypes jdk1.3.1_15 derbyall:derbylang 2005-06-19 06:07:57 ***
> 2492a2493,2497
> > ERROR 38000: The exception 'java.lang.StringIndexOutOfBoundsException: String index out of range: 0' was thrown while evaluating an expression.
> > ERROR XJ001: Java exception: 'String index out of range: 0: java.lang.StringIndexOutOfBoundsException'.
> > ij> values cast ('1.0e-' as DECIMAL(6,2));
> > 1
> > ---------
> 2494,2497d2498
> < ij> values cast ('1.0e-' as DECIMAL(6,2));
> < 1
> < ---------
> < ERROR 22018: Invalid character string format for type DECIMAL.
> Test Failed.
> *** End: floattypes jdk1.3.1_15 derbyall:derbylang 2005-06-19 06:08:56 ***
> Here's a more detailed overview:
> (in all cases ERROR 22018 is: : Invalid character string format
> for type DECIMAL
> ERROR 38000 is: The exception
> 'java.lang.StringIndexOutOfBoundsException: String index out of
> range: 0' was thrown while evaluating an expression.
> ERROR XJ001: Java exception: 'String index out of range: 0:
> java.lang.StringIndexOutOfBoundsException'.
> -------
> statement @ line 2462 of floattypes.out
> values cast('1e+0' as DECIMAL(6,2));
> jdk14/5 output 1.00
> jdk131 output 1.00
> ibm131 output 1.00
> j9_13 output ERROR 22018
> ---------
> statement @ line 2466 of floattypes.out
> values cast('+-1e+1' as DECIMAL(6,2));
> jdk14/5 output ERROR 22018
> jdk131 output ERROR 22018
> ibm131 output -10.00
> j9_13 output ERROR 22018
> ----------
> statement @ line 2470 of floattypes.out
> values cast('-1e+1' as DECIMAL(6,2));
> jdk14/5 output -10.00
> jdk131 output -10.00
> ibm131 output -10.00
> j9_13 output ERROR 22018
> ----------
> statement @ line 2498 of floattypes.out
> values cast('1.0e+' as DECIMAL(6,2));
> jdk14/5 output ERROR 22018
> jdk131 output ERROR 38000 and XJ001
> ibm131 output ERROR 38000 and XJ001
> j9_13 output ERROR 22018
> ------------------------------------------
> All in all, I suggest we stop running this test under these jvms, until someone is interested in resolving this some other way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.