|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I was using java 1.6. Have now upgraded to 1.8. Makes no difference.
Currently using Jenkins version 1.565. Will look into upgrading to the latest version tomorrow.
I have however noticed the following:
My setup is a 32bit windows 7 Jenkins master, and a 64bit windows 7 Jenkins slave.
I run a multi-configuration job, and archive the results from all configurations.
After the job is done, I manually check the archive folders in the jenkins master.
The timestamps for the configurations that ran on the slave are fine. It is only the timestamps for the configurations that ran in the master which are incorrect.
So the problem seems to be connected to running on 32bit windows, or to jobs running on the jenkins master...