DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40636>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40636 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-17 13:40 ------- I think this can be closed as "not a bug". If you change the system clock while running a Jmeter test, the time measurements will become wrong, and you risk getting negative durations. Look for example at : http://forum.java.sun.com/thread.jspa?threadID=640637&messageID=3766162 (Look at the post "Jun 30, 2005 9:49 AM (reply 4 of 16)" and ignore the rest) >From the bug report, one can see that the "ntpd deamon" has set the clock back 0.5 seconds " Sep 28 22:22:00 xx ntpd[950]: time reset -0.497615 s Sep 28 22:22:00 xx ntpd[950]: synchronisation lost " So I think this bug can be closed until someone reports problems with negative time recorded, and the system clock has not been adjusted in the period where the test was executed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
