Skip to content
Snippets Groups Projects
Select Git revision
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • develop default protected
  • feature/composite-scheme
  • hyperplastic
  • feature/local-dt-fsi
  • feature/kinetic-schemes
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • feature/escobar-smoother
  • feature/hypoelasticity-clean
  • feature/hypoelasticity
  • feature/Navier-Stokes
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
32 results

mpi_test_main.cpp

  • Stéphane Del Pino's avatar
    4c53bd36
    Change tests running policy · 4c53bd36
    Stéphane Del Pino authored
    Do not use `ctest` anymore, tests are now launch directly (manually)
    using generated unit tests binaries (unit_tests and mpi_unit_tests)
    
    `ctest` can always be invoked but not using `make test`.
    
    The reason for this change is that `ctest` runs a binary for each test
    which is not what we want now. The goal of this development is to
    provide a mesh database that is built **once** for all: the cost of
    building meshes could be prohibitive and their multiplication should
    be avoided for obvious performances and storage reasons.
    4c53bd36
    History
    Change tests running policy
    Stéphane Del Pino authored
    Do not use `ctest` anymore, tests are now launch directly (manually)
    using generated unit tests binaries (unit_tests and mpi_unit_tests)
    
    `ctest` can always be invoked but not using `make test`.
    
    The reason for this change is that `ctest` runs a binary for each test
    which is not what we want now. The goal of this development is to
    provide a mesh database that is built **once** for all: the cost of
    building meshes could be prohibitive and their multiplication should
    be avoided for obvious performances and storage reasons.