You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mark Hindess (JIRA)" <ji...@apache.org> on 2006/05/17 10:38:05 UTC
[jira] Created: (HARMONY-468) CalendarTest compareTo test is
unstable
CalendarTest compareTo test is unstable
---------------------------------------
Key: HARMONY-468
URL: http://issues.apache.org/jira/browse/HARMONY-468
Project: Harmony
Type: Bug
Components: Classlib
Reporter: Mark Hindess
Priority: Minor
Attachments: unstable.calendar.test.diff
test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
The reason is that getInstance creates an entry with the current second and millisecond values. The
set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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: (HARMONY-468) CalendarTest compareTo test is
unstable
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-468?page=all ]
George Harley closed HARMONY-468:
---------------------------------
Verified by Mark.
> CalendarTest compareTo test is unstable
> ---------------------------------------
>
> Key: HARMONY-468
> URL: http://issues.apache.org/jira/browse/HARMONY-468
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Mark Hindess
> Assignee: George Harley
> Priority: Minor
> Attachments: unstable.calendar.test.diff
>
> test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
> The reason is that getInstance creates an entry with the current second and millisecond values. The
> set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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: (HARMONY-468) CalendarTest compareTo test is
unstable
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-468?page=all ]
Mark Hindess updated HARMONY-468:
---------------------------------
Attachment: unstable.calendar.test.diff
I think the first test is the only one that is really going to be a problem but the patch adds clear calls to before all the set calls in this test.
> CalendarTest compareTo test is unstable
> ---------------------------------------
>
> Key: HARMONY-468
> URL: http://issues.apache.org/jira/browse/HARMONY-468
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Mark Hindess
> Priority: Minor
> Attachments: unstable.calendar.test.diff
>
> test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
> The reason is that getInstance creates an entry with the current second and millisecond values. The
> set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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] Resolved: (HARMONY-468) CalendarTest compareTo test is
unstable
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-468?page=all ]
George Harley resolved HARMONY-468:
-----------------------------------
Resolution: Fixed
Hi Mark,
Patch committed in revision 407228. Please could you verify that it has been applied as you expect.
Many thanks for this test improvement.
Best regards,
George
> CalendarTest compareTo test is unstable
> ---------------------------------------
>
> Key: HARMONY-468
> URL: http://issues.apache.org/jira/browse/HARMONY-468
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Mark Hindess
> Assignee: George Harley
> Priority: Minor
> Attachments: unstable.calendar.test.diff
>
> test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
> The reason is that getInstance creates an entry with the current second and millisecond values. The
> set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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] Assigned: (HARMONY-468) CalendarTest compareTo test is
unstable
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-468?page=all ]
George Harley reassigned HARMONY-468:
-------------------------------------
Assign To: George Harley
> CalendarTest compareTo test is unstable
> ---------------------------------------
>
> Key: HARMONY-468
> URL: http://issues.apache.org/jira/browse/HARMONY-468
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Mark Hindess
> Assignee: George Harley
> Priority: Minor
> Attachments: unstable.calendar.test.diff
>
> test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
> The reason is that getInstance creates an entry with the current second and millisecond values. The
> set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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: (HARMONY-468) CalendarTest compareTo test is
unstable
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-468?page=comments#action_12412166 ]
Mark Hindess commented on HARMONY-468:
--------------------------------------
Looks good. Thanks George.
> CalendarTest compareTo test is unstable
> ---------------------------------------
>
> Key: HARMONY-468
> URL: http://issues.apache.org/jira/browse/HARMONY-468
> Project: Harmony
> Type: Bug
> Components: Classlib
> Reporter: Mark Hindess
> Assignee: George Harley
> Priority: Minor
> Attachments: unstable.calendar.test.diff
>
> test_compareToLjava_util_Calendar is unstable. (Insert a Thread.sleep(2000) at line 405 to see it fail.)
> The reason is that getInstance creates an entry with the current second and millisecond values. The
> set call retains these values unless clear is called first. So the two identical sets can have different second and millisecond values.
--
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