search for: tigher

...ot of code. In the past we've generally serialized this sort of thing between contributors, or broken changes up to be extremely incremental. The reason this is happening less now is that we, as developers, are growing more ambitious with our fixes to LLVM systematic problems, and doing so on a tigher schedule. Once again, this is a good thing. There's two issues with buildbots. Firstly, we need more buildbots on more platforms. For example, there are no Darwin buildbots, so if I commit a change that breaks Darwin I won't get immediate notice about it, nor a log of the failure. We could...

On Jul 15, 2009, at 4:48 PMPDT, Daniel Dunbar wrote: > That depends on what you call a false positive. The public buildbot > regularly fails because of mailing Frontend tests, and I have had > continues failures of some DejaGNU tests for a long time on some > builders. Its not a false positive per se, but one starts to ignore > the failures because they aren't unexpected. Yes.

...ast we've generally serialized this sort > of thing between contributors, or broken changes up to be extremely > incremental. The reason this is happening less now is that we, as > developers, are growing more ambitious with our fixes to LLVM systematic > problems, and doing so on a tigher schedule. Once again, this is a good > thing. +1 > There's two issues with buildbots. Firstly, we need more buildbots on more > platforms. For example, there are no Darwin buildbots, so if I commit a > change that breaks Darwin I won't get immediate notice about it, nor a log...

...> generally serialized this sort of thing between contributors, or > broken changes up to be extremely incremental. The reason this is > happening less now is that we, as developers, are growing more > ambitious with our fixes to LLVM systematic problems, and doing so > on a tigher schedule. Once again, this is a good thing. > > There's two issues with buildbots. Firstly, we need more buildbots > on more platforms. For example, there are no Darwin buildbots, so if > I commit a change that breaks Darwin I won't get immediate notice > about it, nor...