Dann Corbit wrote:
> Perhaps all that is needed is some sort of automated, formal reporting
> procedure.  For example, a large test set might be created that runs a
> thorough regression feature list.  When the test completes, a data file
> is emailed to some central repository, parsed, and stored in a database.

I do have an automated build/initdb/regression that I run every night
and email the results to myself.

        [ "X$1" != "X-n" ] && CLEAN="-c" && shift
        . /etc/profile
        rm -r /u/pg/data
        # return command error value
        (pgmakeall $CLEAN 2>&1; echo "$?" > $TMP/ret) | 
                (tee  $TMP/0; exit `cat $TMP/ret`) &&
        aspg initdb &&
        pgstart &&
        newdb test &&
        cd /pg/test/regress &&
        gmake clean &&
        aspg gmake installcheck
        grep warning $TMP/0 | 
                grep -v setproctitle | 
                grep -v find_rule | 
                grep -v yy_flex_realloc |
                grep -v '\[javac\] 1 warning'

I also run this after I apply patches.

  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to