Daniel Quinlan <[EMAIL PROTECTED]> writes: > SA testing actually moves really fast and it generates really good rules > that we *could* use the very next morning (we run tests at 0900 UTC > which is the lowest ebb of the developer's development activity).
more fun with histograms: check-in time since the beginning of the tree: hour frequency 0 *************************************************+ 1 *********************************** 2 ************************ <- this is when mass-checks start 3 ************************ 4 ***************************+ 5 ***********************+ 6 **********************************+ 7 *******************************************+ 8 ******************************************* 9 ************************************************ 10 ********************************************** 11 ***************************************************+ 12 **************************************************** 13 ************************************************************** 14 ********************************************************+ 15 *************************************************************** 16 ************************************************************* 17 **************************************************************+ 18 *********************************************************************** 19 ******************************************************************** 20 *************************************************************+ 21 ***********************************************************+ 22 ******************************************************************+ 23 ************************************************* The hour is specified as PDT, so "2" is 0900 to 1000 UTC. We start the nightly check at 0900 UTC. I should mention that you don't actually need to install 3.0 to run nightly mass-checks since mass-check is designed to be run in-place in an uninstalled tree. Everyone (not just committers) who submits nightly results just has a cron job or two that runs each night. We have scripts to do the svn updates, rsyncs, etc. for you. You do need to get an account on the rsync server, but that's easy. Daniel -- Daniel Quinlan anti-spam (SpamAssassin), Linux, http://www.pathname.com/~quinlan/ and open source consulting
