|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I'm not convinced that nanoseconds precision is a good thing.
It cannot be used for the "system clock time", because System.nanoTime() returns the number of nanoseconds since some fixed but arbitrary origin time (quoting the Javadoc). So there is no way to combine it with the number of milliseconds returned by System.currentTimeMillis() or new Date().
It could be used for the "elapsed time", but I can't think why anyone would want this level of precision unless they are trying to use the Timestamper plugin for micro-benchmarking. And it is poorly suited for micro-benchmarking; the timings would be inaccurate due to the other work done by Jenkins between measurements.
I understand that you wanted to include the nanoseconds for use in anchor names, but I think this can be done in other ways. I've put some ideas into JENKINS-21208.