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/10 00:50:27 UTC
[jira] Created: (DERBY-2225) error with weme 6.1. in test
timestampArith.java
error with weme 6.1. in test timestampArith.java
------------------------------------------------
Key: DERBY-2225
URL: https://issues.apache.org/jira/browse/DERBY-2225
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.3.0.0
Environment: j9_foundation 1.1 (as comes with weme 6.1)
Reporter: Myrna van Lunteren
Assigned To: Myrna van Lunteren
Priority: Minor
test lang/timestampArith fails with j9_foundation 1.1.:
(from the .tmp:)
Test timestamp arithmetic starting.
Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
This is likely a jvm problem. So I'll not mark this as a regression.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2225) error with weme 6.1. in test
timestampArith.java
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467102 ]
Myrna van Lunteren commented on DERBY-2225:
-------------------------------------------
This is fixed in version weme 6.1.1. So, that is the version of j9 one needs to run derbyall. With revision 499506 ( http://svn.apache.org/viewvc?view=rev&revision=499506) I removed the canon file I had checked in earlier (with revision 497678).
> error with weme 6.1. in test timestampArith.java
> ------------------------------------------------
>
> Key: DERBY-2225
> URL: https://issues.apache.org/jira/browse/DERBY-2225
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.0.0
> Environment: j9_foundation 1.1 (as comes with weme 6.1)
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
>
> test lang/timestampArith fails with j9_foundation 1.1.:
> (from the .tmp:)
> Test timestamp arithmetic starting.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> This is likely a jvm problem. So I'll not mark this as a regression.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2225) error with weme 6.1. in test
timestampArith.java
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-2225.
-------------------------------------
Resolution: Invalid
This is indeed a jvm problem. Referred to vendor.
> error with weme 6.1. in test timestampArith.java
> ------------------------------------------------
>
> Key: DERBY-2225
> URL: https://issues.apache.org/jira/browse/DERBY-2225
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.0.0
> Environment: j9_foundation 1.1 (as comes with weme 6.1)
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
>
> test lang/timestampArith fails with j9_foundation 1.1.:
> (from the .tmp:)
> Test timestamp arithmetic starting.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> This is likely a jvm problem. So I'll not mark this as a regression.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2225) error with weme 6.1. in test
timestampArith.java
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465937 ]
Myrna van Lunteren commented on DERBY-2225:
-------------------------------------------
The problem is in the calculation of GregorianCalendar(<someint>, -1). Sometimes (some conditions: no getTimeInMillis or getTime calls before the add), that results in an incorrect Day (in the repro I managed to make, DAY_OF_MONTH is wrong in the toString() method after the add call).
> error with weme 6.1. in test timestampArith.java
> ------------------------------------------------
>
> Key: DERBY-2225
> URL: https://issues.apache.org/jira/browse/DERBY-2225
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.0.0
> Environment: j9_foundation 1.1 (as comes with weme 6.1)
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
>
> test lang/timestampArith fails with j9_foundation 1.1.:
> (from the .tmp:)
> Test timestamp arithmetic starting.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> Unexpected result from 'values( {fn TIMESTAMPADD( SQL_TSI_FRAC_SECOND, -1000,{d '2005-05-11'})})'. Expected 2005-05-10 23:59:59.999999 got 2005-05-11 23:59:59.999999.
> This is likely a jvm problem. So I'll not mark this as a regression.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira