|
||||||||
|
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/d/optout.
Below is code related to this issue.
Looks like the magic number Jenkins core has hardcoded insite it is 1000 miliseconds. Code below in a patch here:
http://git.eclipse.org/c/hudson/org.eclipse.hudson.core.git/commit?id=97587dde35e862fabbd8b5b4b0136a786cfcff37 .
This is an issue when using VMs where time can drift quite quickly. Would be good to disable this test, or to be able to change the magic number of seconds in configuration.
@@ -151,21 +144,22 @@ public final class TestResult extends MetaTabulatedResult {
}
}
if(!parsed) {
+ if (!parsed) {
long localTime = System.currentTimeMillis();
if(localTime < buildTime-1000) /margin/
// build time is in the the future. clock on this slave must be running behind
+ if (localTime < buildTime - 1000) /margin/ // build time is in the the future. clock on this slave must be running behind
+ { throw new AbortException( - "Clock on this slave is out of sync with the master, and therefore \n" + - "I can't figure out what test results are new and what are old.\n" + - "Please keep the slave clock in sync with the master."); + "Clock on this slave is out of sync with the master, and therefore \n" + + "I can't figure out what test results are new and what are old.\n" + + "Please keep the slave clock in sync with the master."); + }