On Sat, May 7, 2011 at 8:48 PM, Dimitri Rodis <dimit...@integritasystems.com > wrote:
> I hate to break it to you guys, but this has been an issue for quite a > while in the 2.0 builds (8-9 months now). Not quite sure what started it > happening, but I did experience this behavior way back then, and still do > when I try the builds on it every now and then. > Well if you know that it has been happening for a number of months you should have check into it right away. Builds remain on the snapshot server for almost a month (it looks like, there are 38 builds there right now). Now those older builds don't seem to be available anymore it will not be as easy to find the approximate commit that causes the problem. A general overview of how to find a bad commit (what I do at least): Download the last build, try it and see if you have the problem. If not, you know the change was made after it. If you have the problem, move back to another build and try again. - Y
