[Dune-devel] parallel tests in dune-common

Carsten Gräser graeser at mi.fu-berlin.de
Mon Dec 1 11:59:04 CET 2014

Hi Christoph,

Am 01.12.2014 um 11:43 schrieb Christoph Grüninger:
> Hi Carsten,
> I know. The reason it, they are not disabled by the build system but
> return 77. This indicates a skipped test for the Autotools, in CMake
> this was not supported until CMake 3.0.
> Maybe we should decide in general, whether the build system should
> disable the test silently or that it should indicate the skipped test. I
> prefer to get "x test skipped" and would like to make the change. The
> problem is, that it will only work properly with CMake 3.0.
> Or we use a hack with a script that evaluates the return value and
> changes a 77 into a 0. Mhh.
given the following options

a) Let the tests fail until we require cmake 3.0
b) Silently disable the tests if cmake <3.0
c) Provide a hack that disables pretends that the tests have passed.
d) Make tests pass if their preconditions are not matched
   (i.e. sequential dune)

my ranking would be b) > c) > d) > a).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20141201/ec41d510/attachment.pgp>

More information about the Dune-devel mailing list