Hi Gary,
Functional changes look okay to me.
Thanks,
David
On 10/11/2011 5:21 AM, Gary Adams wrote:
Here's an update diff for the elapsed time check.
- added current CR# to @bug tag
- moved capture of start time to after creation of the latches
so only the schedule*() and the await() calls are
Here's an update diff for the elapsed time check.
- added current CR# to @bug tag
- moved capture of start time to after creation of the latches
so only the schedule*() and the await() calls are included
in the elapsed time check.
jdk/test/java/util/Timer/Args.java
/*
* @te
On 11/ 6/11 08:05 PM, David Holmes wrote:
Hi Gary,
On 4/11/2011 11:36 PM, Gary Adams wrote:
I've started to look at timing related bugs that have been open
for a while, but have not had sufficient priority to make it to the
top of the list of bugs to be fixed. Thought I'd start with some
low h
On 07/11/2011 01:05, David Holmes wrote:
Sometimes apparently low-hanging fruit is attached to the tree with
steel wire ;-) (and sometimes barbed wire at that)
In the case of some of our tests then it's actually fuse wire, with a
nice little surprise when you yank at it :-)
Hi Gary,
On 4/11/2011 11:36 PM, Gary Adams wrote:
I've started to look at timing related bugs that have been open
for a while, but have not had sufficient priority to make it to the
top of the list of bugs to be fixed. Thought I'd start with some
low hanging fruit with simple bug fixes.
Someti
I've started to look at timing related bugs that have been open
for a while, but have not had sufficient priority to make it to the
top of the list of bugs to be fixed. Thought I'd start with some
low hanging fruit with simple bug fixes.
6731620: TEST_BUG: java/util/Timer/Args.java is too optimi
