You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "George Harley (JIRA)" <ji...@apache.org> on 2006/05/17 17:16:08 UTC
[jira] Closed: (HARMONY-468) CalendarTest compareTo test is
unstable
[ 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