RE: Log file assertion

> > I think your theory holds water. If I delete the builds as you say
it
> > works. So I think the count needs to be written back sooner?
> 
> Yeah, that sounds like a good idea. I'll add a save() call just after
the
> build gets started. It isn't as easy as I thought, there's some issue
with
> saving Builds that haven't finished yet (you want the on-disk
> representation
> to look like an interrupted build, since if you ever load that copy,
> that's
> what must have happened). But I'll get to it soon.

It appears to happen if you have a build fail, stop the master to fix a
config problem, and then restart, which is a little annoying! :-)
Perhaps, as well as saving the build state you could save the count
somewhere else, so if the build state gets whacked you can start from
the build count to avoid this problem?

Nick




-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_idt02&alloc_id135&op=click