I upgraded to version 1.4.2 of CC and I have not seen this problem (it has been a week and I use to see this error a couple of times a day). Keeping my fingers crossed.
On Feb 19, 8:21 am, Helmut <[email protected]> wrote: > > I just noticed something : > > the modification has a datetime of : > > <date>2009-02-10 02:05:17</date> > > > and the build is fired at : > > <build date="2009-02-11 02:00:00" buildtime="00:00:01" /> > > > how can there be modification in the future? > > modification is on 2/10 and build on 2/11 which should be okay. > > The problem is in the way CC is requesting the source code fromAccuRev(at > least that is whatAccuRevsupport) explained to me. For > some reason it is picking a transaction that is older than the current > version of the files which will cause it to fail. > > In my case I have checked the server time against the build machine > and synched them several times. I have doen the same with my machine > and theAccuRevserver. If there is a problem with the time between > theAccuRevserver and another machine it will usually give you a > warning or an error telling you about the timing being off between the > machines. > > I have thought about creating a trigger based on project failure to > automatically do a rebuild but I think this could be a problem too if > the failure id due to a real code problem. I could have a continuous > build problem. > > If anyone has ideas or thoughts on what we can try please contact me. > > thank you, > Helmut
