Skip to content

Testing Infrastructure

Jump to bottom
Timo Heister edited this page May 27, 2020 · 17 revisions

This documents the testing infrastructure and who it is administrating it.

Continuous Integration

All pull-requests on github are tested with the following machines and their status is reported on the pull request itself:

  1. indentation (name: continuous-integration/travis-ci/pr): Checks the indentation by running ./contrib/utilities/check_indentation.sh and checking that there are no changes detected. Runs on https://travis-ci.org/. Maintained by: deal.II developers. Configuration stored in /.travis.yml.

  2. CI (running on https://jenkins.tjhei.info/job/dealii/ and controlled by ./Jenkinsfile). This tests indentation and (currently) build with and without MPI and runs a selection of tests. See the Jenkinsfile for details and https://github.com/tjhei/candi/tree/docker#candi-docker-images for the Docker images used. Maintained by: @tjhei

  3. OSX (running on https://jenkins.tjhei.info/job/dealii-OSX/ and controlled by ./contrib/ci/Jenkinsfile.osx). Compiles under OSX. Maintained by: @tjhei

  4. tidy (running on https://jenkins.tjhei.info/job/dealii-tidy/ and controlled by ./contrib/ci/Jenkinsfile.tidy). Runs clang-tidy (by running ./contrib/utilities/run_clang_tidy.sh). Maintained by: @tjhei

  5. github- simple build running inside "Github Actions" in several configurations (currently Linux, windows, OSX). Configured using ./.github/workflows). The virtual machines only have 2 cores, so no tests are being run due to time constraints.

  6. MSVC - appveyor A Windows build using https://appveyor.com, controlled via ./contrib/ci/appveyor.yml.

Note: PRs are not run automatically but need to be approved by one of the developers by adding the label "ready to test" to the PR. From now on, every push to this PR will cause a new build. To build the original build or to rebuild the last commit (maybe because the tester crashed), trigger a new build by leaving a comment containing the text /rebuild.

Regression testing

In addition to testing pull requests, we also continuously have machines execute the current master branch with different configurations. The results are reported at https://cdash.43-1.org and documentation can be found at https://www.dealii.org/developer/developers/testsuite.html#build_tests

We currently have the following machines running:

  1. tester: The only machine in the "Regression tests" category on cdash. Many configurations. Located in Minneapolis and maintained by @tamiko
  2. simserv04: One of the machines in the "Continuous" category on cdash. Some older configurations. Located in Heidelberg and maintained by @tamiko
  3. simserv02: One of the machines in the "Continuous" category on cdash. Running the Intel compiler. Maintained by @masterleinad
  4. davyddenubuntu: One of the machines in the "Continuous" category on cdash. A configuration with all dependencies but CUDA enabled and built via Spack with and without optimization flags on Ubuntu 16.04 with GCC 5.4.0. Maintained by @davydden
  5. CUDA10 : One of the machines in the "Continuous" category on cdash. Configuration with CUDA 10. Maintained by @Rombur
Clone this wiki locally