Robert K authored 4 years ago and Simon Praetorius committed 3 years ago

trigger the core pipeline in dune-nightly-tests

run downstream tests in separate stage

Allow failure for triggered downstream pipeline

Simon Praetorius authored 4 years ago and Andreas Dedner committed 4 years ago

switch to docker registry in dune-project.org

use debian11 from dune gitlab registry

This is a workaround for a bug that showed up after gitlab migration. See issue
infrastructure/issues0#62 for further
discussion.

Robert K authored 4 years ago and Andreas Dedner committed 4 years ago

Python bindings, default is OFF.

[feature][CI] enable Python bindings.

make sure DUNE_ENABLE_PYTHPMBINDINGS is set to true in dune-py

Other implementations should only be selected if the compiler is specifically
told to support them.

Closes: #165

All of the other modules don't specify the quick label on their tests.

The special vectorization test run stays in the local configuration, as it is specific to
dune-common.

This adds build that runs expensive tests, including Vc on with at least AVX.
The build is allowed to fail to compensate for the possibility of no runner
beeing available.

Debian 8 is not supported anymore.

This way dependencies installed via `duneci-install-module` are built
with the same options as the module to be tested.

 - Added:   Debian 10 with gcc in C++17 mode
 - Removed: Debian 8 + Backports with clang

Reference: http://lists.dune-project.org/pipermail/dune-devel/2017-July/002224.html

gcc 5.4 and clang 3.8.

Reference: core/dune-common#37