Re: [CFARM] Script for automatic checking of patches

[Zdenek Dvorak <rakdver at kam dot mff dot cuni dot cz>]

Hello,

> > > I'm still quite annoyed by the fact that when new fails are inserted
> > > in trunk, there is no way to filter out these new fails from the fails
> > > due to the tested patch.  One possible solution is to schedule every
> > > now and then a bootstrap of a pristine tree to reset the set of
> > > passing tests, but this can be done outside the tester.
> > 
> > what we do in our tester is that we build gcc twice (once without the
> > patch, once with) and compare the results.  It doubles the time of the
> > testing, but the results are more reliable than with the scheme you
> > propose.
> 
>    But if you test N patches against the same revision, the time will be
> N+1, which is a lot for N=1 but not bad at N=10. The compile farm is fast
> enough that you can do so before GCC changes a lot.

except that in many cases you want to prescribe a different revision
-- if you are testing a patch for branch
-- if you want to be sure that the change is correct with the most
   current sources

Zdenek