dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Thu, Feb 03, 2011 at 04:06:18PM -0800, Johan Hake wrote:
> On Thursday February 3 2011 16:02:32 Anders Logg wrote:
> > On Thu, Feb 03, 2011 at 03:57:30PM -0800, Johan Hake wrote:
> > > On Thursday February 3 2011 15:46:33 Anders Logg wrote:
> > > > On Thu, Feb 03, 2011 at 11:57:36PM +0100, Marie E. Rognes wrote:
> > > > > On 3. feb. 2011, at 22:21, Anders Logg <logg@xxxxxxxxx> wrote:
> > > > > > [\snip]
> > > > > >
> > > > > > Any thoughts?
> > > > >
> > > > > How about some or all of these:
> > > > >
> > > > > 1. Not introducing separate developer branches
> > > >
> > > > Too late. ;-)
> > > >
> > > > > 2. Establishing a subset of tests that take a few minutes to run, so
> > > > > that we actually bother to run a set of tests before pushing to the
> > > > > main branch
> > > >
> > > > That would be useful, but it's probably difficult to design such a
> > > > test. Perhaps it would be one single main.cpp that does a whole lot of
> > > > things.
> > >
> > > We have the unit tests. They should always be run before committing
> > > stuff. We could definitely increase the number of unit tests and the
> > > scope of them.
> >
> > The problem is it takes time to (re)-build the tests. With just one
> > executable, we would have something that is quick enough that one
> > would always try it. (Not that I'm insisting that we must add this.)
>
>   python test.py --only-python
>
> works for me ;)

I had forgotten about that. Yes, that's useful!

Maybe we could add a make target for that? So one can stand in the
build directory and type

  make quicktest

--
Anders