From simon.praetorius at tu-dresden.de Fri Nov 6 17:41:54 2026 From: simon.praetorius at tu-dresden.de (Simon Praetorius) Date: Fri, 6 Nov 2026 17:41:54 +0100 Subject: [Dune-devel] New system-test infrastructure Message-ID: <2d6eee4e-64ac-4f84-960e-ec59a69b4549@tu-dresden.de> Hi everyone, I have now merged an update of the infrastructure/dune-nightly-test setup. This project defines our system tests. Before the merge, we had two branches that separately specified a core and a full-system test pipelines. The corresponding trigger were only available in dune-common. This is changed now. The master branch defines all pipelines by a selection mechanism. We select a subset of jobs that run in a core-selection and a full-selection pipeline. Also, these system pipeline triggers are now included in the core/ci-config default gitlab-ci.yml includes. Thus, every module that includes it can run system pipelines and test changes against all other modules in the chain. Thereby, upstream modules are only compiled, while downstream modules are built and tested.  There are some ways to control the system test selection, see the MR description https://gitlab.dune-project.org/infrastructure/dune-nightly-test/-/merge_requests/16 Most of this is done automatically by the ci-config trigger jobs. I expect that some configurations and selections do not work out-of-the box correctly. One cannot really test all the interaction between several project's ci configuration without merging corresponding branches. Please report unexpected behavior when running these triggered pipelines. Currently, this can be done manually and is not required. In particular, the situation that we want some branches of different modules to be tested together might still fail. Currently many tests fail due to our runners that are on their limits. Often out of disk space. Also, the gcc-12.2.0 compiler shipped with debian-12 has several bugs that trigger wrong compiler errors or even internal compiler errors. That's why I switched to gcc-12.4.0 from debian-13 instead, where some of the bugs are already fixed. Happy testing, Simon -- Simon Praetorius [er/ihm; he/him] Wissenschaftlicher Mitarbeiter Institut für Wissenschaftliches Rechnen Technische Universität Dresden Tel: TUD-34432 Web: tu-dresden.de/Members/simon.praetorius Mail: simon.praetorius at tu-dresden.de