I'm also suffering from bug #16 where Jamon mixes up nanoseconds and milliseconds. Would it be possible to include a patch for this in a future version? A simple workaround is to declare a field startTime in TimeMonNano shadowing the one from TimeMon. With very short measurements the average value will however stay at 0 - it is measured in milliseconds.
Otherwise, very happy with Jamon!
I apologize for the delay in responding. I haven't been notified lately with jamon emails for some reason and a few slipped by me.
I can look into that. I hope to make another release in jamon over the next couple weeks.
This will be released in 2.79. I changed the code and committed.
Here is the commit: https://sourceforge.net/p/jamonapi/jamonapi/ci/7f026e8eaa46df1ce98fc894678f772b099f8db7/
The fix for this was released today.
Log in to post a comment.