| Since few days, nunit-plugin started to complain about clocks being out of sync after the test report is generated correctly. In fact, initially it was right, clocks drifted about 4 or 5 seconds and I took the measures to avoid that (they syncronize with an NTP server every hour, just to assure the synchronization throghout the day). However, nunit-plugin still complains, and now all the clocks are synchronized. This is the exact message I get: Recording NUnit tests results
ERROR: Step ‘Publish NUnit test result report’ failed: Clock on this slave is out of sync with the master, and therefore
I can't figure out what test results are new and what are old.
Please keep the slave clock in sync with the master. There are two things that can be wrong here:
- The message, since it is basically false (clocks are NOT out of sync)
- The way this plugin checks the synchronization between the clocks
Also, as a side note, in my opinion I don't fully understand why is necessary to have the clocks synchronized to the millisecond since all the testing process takes place on the Agent. I only want the report.xml to be parsed and shown regardless its time. In fact, since the entire workspace is cleaned out before starting the tests, the only existing report.xml has to be the most recent --> just take it! |
