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)" <de...@db.apache.org> on 2006/01/09 21:11:39 UTC
[jira] Created: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
test lang/floattypes fails with jdk 1.3 based jvms
---------------------------------------------------
Key: DERBY-804
URL: http://issues.apache.org/jira/browse/DERBY-804
Project: Derby
Type: Bug
Versions: 10.1.2.0
Environment: failure occurs in 10.1 branch, and on main branch.
Reporter: Myrna van Lunteren
Priority: Minor
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=all ]
Mike Matrigali updated DERBY-804:
---------------------------------
Component: Test
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.1.2.0, 10.2.0.0
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-804) test lang/floattypes fails with jdk
1.3 based jvms
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=comments#action_12432070 ]
Andrew McIntyre commented on DERBY-804:
---------------------------------------
Committed _skipcomment patch to trunk with revision 439209.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.2.0, 10.2.1.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-804) test lang/floattypes fails with jdk 1.3 based jvms
Posted by Andrew McIntyre <mc...@gmail.com>.
On Jan 20, 2006, at 5:29 AM, Myrna van Lunteren (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-804?
> page=comments#action_12363399 ]
>
> Can a committer please look at committing my patch to stop this
> test from running with jdk131/ibm131 until someone cares to look at
> this otherwise (or we no longer support jdk131, or we collectively
> decide not to fix this).
I'll be glad to disable the test for jdk131, but this looks like a
bug to me. Just looking at the test behavior on the different vms, it
seems like we delegate to a method in the java class libraries that
either fails to parse the string (and we catch this properly) or
returns the correct value, and in this one case the class library
throws an exception which we don't catch, but possibly could
(should?) It's interesting that j9 returns the expected error in this
case.
Dan, any opinion? It seems like we should be catching this, but if
you don't think it's worth chasing down, I can disable the test.
andrew
[jira] Commented: (DERBY-804) test lang/floattypes fails with jdk
1.3 based jvms
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=comments#action_12363399 ]
Myrna van Lunteren commented on DERBY-804:
------------------------------------------
Hi,
Can a committer please look at committing my patch to stop this test from running with jdk131/ibm131 until someone cares to look at this otherwise (or we no longer support jdk131, or we collectively decide not to fix this).
Myrna
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Type: Bug
> Versions: 10.1.2.0, 10.2.0.0
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=all ]
Myrna van Lunteren updated DERBY-804:
-------------------------------------
Derby Info: (was: [Patch Available])
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.2.0, 10.2.1.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-804) test lang/floattypes fails with jdk
1.3 based jvms
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=comments#action_12366367 ]
Andrew McIntyre commented on DERBY-804:
---------------------------------------
Observed this issue in 10.1 as well, merged the patch to disable the test over to 10.1 branch with revision 377802.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.1.2.0, 10.2.0.0
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=all ]
Myrna van Lunteren updated DERBY-804:
-------------------------------------
Version: 10.2.0.0
Environment: jdk131, ibm131, wsdd5.6 (was: failure occurs in 10.1 branch, and on main branch.)
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Type: Bug
> Versions: 10.2.0.0, 10.1.2.0
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=all ]
Myrna van Lunteren updated DERBY-804:
-------------------------------------
Derby Info: [Patch Available]
Made a trivial patch against 10.2, which should also apply against the trunk...to document the skip reason.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.2.0, 10.2.1.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-804) test lang/floattypes fails with jdk
1.3 based jvms
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=comments#action_12363482 ]
Andrew McIntyre commented on DERBY-804:
---------------------------------------
Committed Myrna's patch with revision 370932.
No response to previous query on derby-dev. So, I've applied Myrna's patch to disable the test for 1.3.1 vms until someone has time to fix the test or product behavior or we no longer support 1.3.1. Leaving this JIRA issue open until then.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Type: Bug
> Versions: 10.1.2.0, 10.2.0.0
> Environment: jdk131, ibm131, wsdd5.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: 804tststop.diff, 804tststop.stat
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-804) test lang/floattypes fails with jdk 1.3
based jvms
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-804?page=all ]
Myrna van Lunteren updated DERBY-804:
-------------------------------------
Attachment: DERBY-804_10.2_skipcomment.diff
Attaching a tiny patch to document why this test is getting skipped with jdk131, ibm131, wsdd5.6/wctme5.7.
> test lang/floattypes fails with jdk 1.3 based jvms
> --------------------------------------------------
>
> Key: DERBY-804
> URL: http://issues.apache.org/jira/browse/DERBY-804
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.2.0, 10.2.1.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira