This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [CFARM] Script for automatic checking of patches


On Tue, 2007-07-03 at 17:45 +0200, Zdenek Dvorak wrote:
> 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

>From 2006 to now on average each calendar day trunk has 16.2 commits,
90% percentile is 26 commits and 99% percentile is 46 commits (5 days
have more than 50 commits, max is 146 on 20070606).

The compile farm has enough power to follow individual trunk commits
(if we restrict languages) and now enough disk to store baseline
test results. May be some branches can be followed too.

On the farm it makes sense to run a script that loops to build the
baseline results and then have the patch tester use the latest
available baseline. build directories can be kept for a while,
install directories for a while longer and we can probably keep
baseline test results forever. 

As long as only one of such script run for all farm users
it will be fine :).

Laurent

PS: 2x500GB disks will be installed this week-end on farm machines gcc12
and gcc13, bringing total farm disk space at over 1.5 TB. If needed
we'll update the 3x80 GB system disks to bigger disks so it's
easy to double to 3TB or more.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]