Hi Krishna,
I changed my job to run on the Jenkins master which fixed the issue. If you do not want to do this then to sync the clocks you will need to set the date/time on the server hosting the filesystem (or the node running the job) to the same as the Jenkins server. If they are Unix/Linux boxes then the date command can be used but you will need root access. Hope this helps. Thanks ! On Tuesday, 17 July 2012 15:43:21 UTC+1, krishna kurnala wrote: > Hi Nigel > > I guess, I am facing the same issue, can you please let me know, how have > you fixed the un-synchronized clocks? > > Thanks, > Krishna Chaitanya > > > On Tue, Jul 17, 2012 at 3:52 AM, Nig > <[email protected]>wrote: > >> It was indeed the clocks out of sync between the Jenkins master and the >> file server. >> >> Many thanks Sami ! >> >> >> On Tuesday, 17 July 2012 09:01:14 UTC+1, sti wrote: >> >> If you look at the message from Jenkins, it seems Jenkins is not happy >>> with the last-modified attribute of the xml file. If Jenkins sees the xml >>> file is older than the build, it thinks the file might be a left-over from >>> an earlier build. This is a common mistake if people assume build always >>> start with an empty workspace. It doesn't, unless you specifically >>> configure it to be so. >>> >>> Another possibility is the xml file has actually been checked into the >>> version control by someone. >>> >>> Yet another possibility is clocks aren't synchronized in your Jenkins >>> server, your file server and your version control server. Unsynchronized >>> clocks are an easy way to generate strange errors that are loads of fun to >>> debug! >>> >>> -- Sami >>> >>> Nig kirjoitti 16.7.2012 kello 12.27: >>> >>> > Hi, >>> > >>> > I've installed testng-6.5.2 and version 0.32 of the pulgin but no >>> results are displayed. >>> > >>> > The following is logged in the Console Output: >>> > TestNG Reports Processing: START >>> > Looking for TestNG results report in workspace using pattern: >>> **/testng-results.xml >>> > testng-results.xml was last modified before this build started. >>> Ignoring it. >>> > Saving reports... >>> > Found matching files but did not find any TestNG results. >>> > >>> > The testng-results.xml file is attached. >>> > >>> > Am I doing something wrong ? >>> > >>> > Thanks ! >>> > >>> > <testng-results.xml> >>> >>> >
