Re: cvs head has lots of test failures

[Wu Zhou <woodzltc at cn dot ibm dot com>]

Quoting Elena Zannoni <ezannoni@redhat.com>:

> Mark Wielaard writes:
>  >
>  > We really need an autobuilder to catch such things early.
>
> We really need people to run make check before checking stuff in.
> Please folks be considerate to your fellow coders...

That might not be enough.  People might be working on a older source  
tree.  My idea is to do a cvs merge before attempting to check in  
codes.  And run "make check" on that tree instead.

The idea of autobuilder are also helpful.  I ever put some commands  
together into a so-called script, which can do this in some aspect.   
But I don't do any effort to make it robust.  I put it here if anyone  
is interested.

#!/bin/bash -x

rm -rf ./older-cvs
mv ./latest-cvs/ ./older-cvs
mkdir ./latest-cvs
cd ./latest-cvs/
export CVSROOT=:pserver:anoncvs:anoncvs@sources.redhat.com:/cvs/frysk
cvs login
cvs co frysk

#export 'JAVAC=/opt/gccfr/bin/gcj -C'
#export 'GCJ=/opt/gccfr/bin/gcj'
#export 'GIJ=/opt/gccfr/bin/gij'
#export 'JAR=/opt/gccfr/bin/fastjar'
#export 'GCJH=/opt/gccfr/bin/gcjh'
#export 'GCJ_DBTOOL=/opt/gccfr/bin/gcj-dbtool'
#export 'GCC=/opt/gccfr/bin/gcc'
#export 'CC=/opt/gccfr/bin/gcc'
#export 'CXX=/opt/gccfr/bin/g++'
#export 'JAVA=/opt/gccfr/bin/gij'
#export 'JV_SCAN=/opt/gccfr/bin/jv-scan'

export CCASFLAGS="-g3"
export CFLAGS="-g3"
export CXXFLAGS="-g3"
export GCJFLAGS="-g3"

( mkdir build && cd build && ../frysk/autogen.sh ) 1>autogen.log  
2>>autogen.log

( cd build/frysk-imports/tests && make check ) 1>imports-check.log  
2>>imports-check.log
( cd build/frysk-gtk/tests && make check ) 1>gtk-check.log 2>>gtk-check.log

( cd build && make -j2 ) 1>make-j2.log 2>>make-j2.log
( cd build && make check ) 1>make-check.log 2>>make-check.log

(cd build/frysk-core && ./TestRunner -l FINE) 1>core-tr.log 2>>core-tr.log
(cd build/frysk-sys && ./TestRunner -l FINE) 1>sys-tr.log 2>>sys-tr.log
(cd build/frysk-imports && ./TestRunner -l FINE) 1>imports-tr.log  
2>>imports-tr.log

sudo mkdir -p /var/www/html/frysk/i686/`date '+%Y%m%d'`
sudo cp -f *.log /var/www/html/frysk/ /var/www/html/frysk/i686/`date  
'+%Y%m%d'`


Regards
- Wu Zhou


P.S: I am thinking of revisiting the idea of running the build and  
test automatically in a regular time base.  I am planning to cover  
x86, x86_64 and ppc64. (We have x86_64 available now).  On x86,  
x86_64, we don't need any extra effort to auto build.  But on ppc64,  
extra effort is still needed.