[Dune] Returning Geometries As Objects

[Alexander Schlaich]

Hi all,

if you are interested in such a tool you might wan't to have a look at 
Jenkins, http://jenkins-ci.org/.

We use it to run the tests after every commit, just as Bernd described 
(http://espressomd.org/jenkins/).
It can be fully automated and distributed, so the speed does not matter in 
fact.


Cheers,

Alex



----------  Ursprüngliche Nachricht  ----------

Betreff: Re: [Dune] Returning Geometries As Objects
Datum: Montag, 6. Februar 2012, 19:10:01
Von: Bernd Flemisch <bernd at iws.uni-stuttgart.de>
An: dune at dune-project.org

Hey Christian,

we use for Dumux a CMake/CTest/CDash testing environment,
http://www.dumux.org/dashboard.php
maybe some thoughts are also applicable to the DUNE 
testing environment.

I run a cron job that simply tests every two hours. What I 
think does the trick for at least alerting me is that I 
get an email whenever the situation changes, for example 
if different errors occur or if a test which has passed 
before does not pass anymore. That means that if it is ok 
that a test is not built for a longer period, I do not get 
any unnecessary emails.

What we do not have yet, because it is only available in 
the commercial CDash version, is the following interesting 
feature, which for sure can be achieved by some scripting 
magic: whenever the situation changes, all the 
svn-committers since the last built get notified by email. 
I think that would really help making people alert.

Kind regards
Bernd

On Mon, 06 Feb 2012 18:55:09 +0100
  Bernd Flemisch <bernd at iws.uni-stuttgart.de> wrote:
> Hi Matthias,
> 
>> It's a bit of a different story, but I was really 
>>worried when I
>> first learned about DUNE and saw this:
>> http://autobuild.dune-project.org/buildlog
> 
> I totally agree with you. There are different problem 
>related to this:
> a) the automated buildsystem is extremely slow => few 
>people are
>    willing to use it
> b) many tests are not working, and people don't care, 
>because they say
>    it is already broken, thus I can't run my tests.
> c) it often stays red, because something on the server 
>is broken and
>    the test fails due to this problem, but the admin is 
>not aware of
>    the problem and it only gets fixed slowly.
> 
> I think it would be really important to improve the 
>automated
> tests. As I am the original author I have to admint, 
>that I should
> invest time here, but I'm currently too busy with other 
>work.
> 
> So... if someone does have a good idea, I'd be happy to 
>here how we
> can improve the currently automated test situation.
> 
> Cheers
> Christian
> 
> ___________________________________________________________
> 
> Bernd Flemisch                     phone: +49 711 685 
>69162
> IWS, Universitaet Stuttgart          fax: +49 711 685 
>67020
> Pfaffenwaldring 61        email: 
>bernd at iws.uni-stuttgart.de
> D-70569 Stuttgart        url: 
>www.hydrosys.uni-stuttgart.de
> ___________________________________________________________

___________________________________________________________

Bernd Flemisch                     phone: +49 711 685 
69162
IWS, Universitaet Stuttgart          fax: +49 711 685 
67020
Pfaffenwaldring 61        email: 
bernd at iws.uni-stuttgart.de
D-70569 Stuttgart        url: 
www.hydrosys.uni-stuttgart.de
___________________________________________________________

_______________________________________________
Dune mailing list
Dune at dune-project.org
http://lists.dune-project.org/mailman/listinfo/dune
-------------------------------------------------------------