Hi Brian,
The bug number does help trace the original/stimulus for the test;
you can push the new test as subtask.
line 36: I would probably add a comment with the readable time.
Its nice to know when that if someone had to debug the time on file.
And it's worth a couple of extra characters to add the units (ms) to the
error at line 70.
Otherwise looks fine.
Roger
On 5/23/2017 3:41 PM, Brian Burkhalter wrote:
For issue [1] I wrote a test [2] which subsumes the test in the issue report
and ran it on the usual platforms via a regression job including the core
java.io tests and I did not observe the reported failure. Therefore this issue
can simply be resolved as “Cannot Reproduce.” I am wondering however whether it
would be worth adding the new test to the repository anyway, under a new,
different issue ID, of course? In that case would there still be a “@bug” tag
in the test and if so which issue number would it have?
Thanks,
Brian
[1] https://bugs.openjdk.java.net/browse/JDK-6212869
[2] http://cr.openjdk.java.net/~bpb/6212869/webrev.00/
