[Dune] suggestion for testing

[Andreas Dedner]

Ok, 
this seems to be a further approach for extending
our testing - but I still think that our suggestion
of testing against dune-fem should be done.
Also the possibility of adding patches without actual
check in should be considered perhaps also for the 
nightly builds.
Andreas


On Mon, 19 May 2008 09:32:44 +0200
 Oliver Sander <sander at mi.fu-berlin.de> wrote:
> Hi Andreas!
> > All the automated tests run on the same system, and
> > so system specific problems are not caught there.
> >   
> Not quite.  The automated testing system has a
> client/server structure which allows to delegate
> the actual tests to remote machines.
> 
> --
> Oliver
> 
> > Also some problems only occur when using dune with
> > some application, e.g., dune-fem. Therefore testing
> > the dune tar balls with dune-fem on our installation
> > will increase the accuracy of the tests. 
> >
> > Andreas 
> >
> > On Mon, 19 May 2008 09:20:24 +0200
> >  Oliver Sander <sander at mi.fu-berlin.de> wrote:
> >   
> >> Hi!
> >> I agree to all that has been said here, with one
> >> exception:
> >> we already have an infrastructure for automated
> testing,
> >> and the tests you propose should be added there.
> >>
> >> --
> >> Oliver
> >>
> >> Andreas Dedner schrieb:
> >>     
> >>> Hi,
> >>> some of the recent changes to the build system
> >>> are quite fundamental and therefore
> >>> a) difficult to test
> >>> b) rather devastating for users not accustomed to
> >>>    the ''guts'' of the build system.
> >>> We were therefore discussing possibilities of
> >>> increasing the success rate of checkins through
> >>> testing patches on different installations of
> libtool,
> >>> g++ Version etc.
> >>> We have a quite complex nightly build for dune-fem
> >>> using tar balls from the svn head and testing with 
> >>> all kinds of
> >>> grids and similar things. It would not be very
> >>> difficult to add new changes to the repository, e..g,
> >>> the build system after checkout. This would only
> >>> require a patch. This can be easily done by
> >>> sending us a file "patchfile" generated using
> >>>   svn diff > patchfile
> >>> as an email.
> >>> So our suggestion would be: before a major change to
> >>>       
> >> the
> >>     
> >>> build system is committed, the patch could be send to
> >>>       
> >> us
> >>     
> >>> and we add it to our nightly build. The next day
> >>> we know if everything worked out and can either
> commit
> >>> the patch ourself our give an ok for the patch to be
> >>> commit. If something went wrong we can try to figure
> >>> out what the problem was and make a suggestion for
> >>> correcting the problem, which should at least then
> >>> work on our system and others can then try it out on
> >>> there installation.
> >>> Martin would be willing to perform this task on our
> >>>       
> >> side!
> >>     
> >>> And before I forget:
> >>> 1) we would all like to thank Christian for the huge
> >>> amount of work he is investing into the build systen;
> >>> we appreciate how difficult it is and also how
> >>> difficult these change are to test throughly.
> >>> 2) if somebody else would also like to test a patch
> >>> he should just yell. All one has to do is
> >>> run the command
> >>>   patch -p0 < patchfile
> >>>
> >>> Best regards
> >>> the Freiburg team.
> >>>
> >>> PS: tonight we got the following message:
> >>> cd . && ./bin/dunecontrol --only=dune-common m4create
> >>> writing dependencies.m4
> >>>     for dune-common 1.2svn dune at dune-project.org
> >>> { test ! -d dune-common-1.2svn || { find
> >>>       
> >> dune-common-1.2svn
> >>     
> >>> -type d ! -perm -200 -exec chmod u+w {} ';' && rm -fr
> >>> dune-common-1.2svn; }; }
> >>> test -d dune-common-1.2svn || mkdir
> dune-common-1.2svn
> >>> cp: cannot stat `./dune-common.m4': No such file or
> >>> directory
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Dune mailing list
> >>> Dune at dune-project.org
> >>> http://lists.dune-project.org/mailman/listinfo/dune
> >>>   
> >>>       
> >> -- 
> >>
> >>     
> >
>
************************************************************************
> >   
> >> * Oliver Sander                ** email:
> >> sander at mi.fu-berlin.de        *
> >> * Freie Universität Berlin     ** phone: + 49 (30) 838
> >> 75217           *
> >> * Institut für Mathematik II   ** URL  :
> >> page.mi.fu-berlin.de/~sander  *
> >> * Arnimallee 6                 **
> >> -------------------------------------*
> >> * 14195 Berlin, Germany        ** Member of MATHEON
> >> (www.matheon.de)   *
> >>
> >>     
> >
>
************************************************************************
> >   
> >
> >   
> 
> 
> -- 
>
************************************************************************
> * Oliver Sander                ** email:
> sander at mi.fu-berlin.de        *
> * Freie Universität Berlin     ** phone: + 49 (30) 838
> 75217           *
> * Institut für Mathematik II   ** URL  :
> page.mi.fu-berlin.de/~sander  *
> * Arnimallee 6                 **
> -------------------------------------*
> * 14195 Berlin, Germany        ** Member of MATHEON
> (www.matheon.de)   *
>
************************************************************************
>