Local ATDM builds of Trilinos

This directory cmake/std/atdm/ contains a set of *.sh shell scripts and *.cmake files that define a standard ATDM-focused build of Trilinos on a number of different ATDM platforms.

This is used to define a set of automated builds of Trilinos that are run with Jenkins and post to the main Trilinos CDash site using build names that start with Trilinos-atdm. The CTest driver scripts and Jenkins driver scripts that use this ATDM configuration are defined in the Trilinos directory cmake/ctest/drivers/atdm/ (see the README.md file in that directory for details) but these details are not necessary in order to just reproduce a build locally as described below.

Outline:

Quick-start
Installation and usage
checkin-test-atdm.sh
Specific instructions for each system
Troubleshooting configuration problems
Directory structure and contents
Disabling failing tests
Specific systems supported

Quick-start

After cloning the Trilinos git repo on one of the supported ATDM machines, a local configure of Trilinos enabling a few packages is performed as:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh <job-name>

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_<Package1>=ON \
  $TRILINOS_DIR

$ make NP=16  # Uses ninja -j16

$ ctest -j16  # Might need to be run with srun or some other command, see below

The command:

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh <job-name>

determines what machine you are on (using hostname) and then loads the correct environment automatically for that machine and for the build options passed through in <job-name> (or errors out if the current machine is not one of the supported machines).

The <job-name> argument is a single string of the form XXX-<keyword0>-<keyword1>-.... The standard order and format of this string is:

<compiler>-<debug_or_opt>-<kokkos_threading>-<kokkos_arch>

Each of these keywords are described below.

<compiler>: The following lower case <job-name> keywords specify the <COMPILER> variable include:

gnu: Use the GCC compilers (<COMPILER>=GNU)
intel: Use the Intel compilers (<COMPILER>=INTEL)
clang: Use the LLVM Clang compilers (<COMPILER>=CLANG)
cuda: Do a CUDA build (<COMPILER>=CUDA, NODE_TYPE=CUDA)
- cuda-8.0: Use CUDA 8.0
- cuda-9.0: Use CUDA 9.0

When using gnu, intel, clang, and cuda without specifying a version (e.g. cuda-9.0), then a default version of the compilers for that system will be chosen (see the loaded env for the default chosen version). Each system may only support a subset of these compilers; see the cmake/std/atdm/<system-name>/environment.sh file for details on which compilers and which versions are supported. If you choose a compiler that is not supported, an error message will be provided. If default is used, then the default compiler for the system will be selected.

<debug_or_opt>: The following <job-name> keywords specify debug or optimized build and the <BUILD_TYPE> variable (used for the CMake cache var CMAKE_BUILD_TYPEwith default <BUILD_TYPE>=DEBUG):

debug: Use <BUILD_TYPE>=DEBUG
opt: Use <BUILD_TYPE>=RELEASE

<kokkos_threading>: The following <job-name> keywords determine the Kokkos threading model variable <NODE_TYPE> (default is <NODE_TYPE>=SERIAL unless <COMPILER>=CUDA):

openmp: Use OpenMP for host threading (NODE_TYPE=OPENMP)
pthread: Use Pthreads for host threading (NODE_TYPE=THREAD)
serial: Use no host threading (NODE_TYPE=SERIAL, DEFAULT)

If cuda (or cuda-8.0, cuda-9.0, etc.) is given, then <NODE_TYPE> is automatically set to CUDA.

<kokkos_arch>: The <job-name> string can also contain keywords to determine the KOKKOS_ARCH option of the build. This is the case-sensitive architecture name that is recognized by the CMake KOKKOS_ARCH configure option for Trilinos and Kokkos. Some common supported Kokkos architectures for the host node include BDW, HSW, Power8, Power9, and KNL. When a GPU is present, some common Kokkos architecture options include Kepler37 and Pascal60. If one selects a KOKKOS_ARCH value that is not supported by the current system or selected compiler, then the load-env.sh script will return an error message listing the value choices for KOKKOS_ARCH for each supported compiler.

Note that currently only a single KOKKOS_ARCH value is recognized in the <job-name> string and it must be proceeded a dash '-' such as with intel-KNL or cuda-Kepler37. This setup does not currently support specifying multiple KOKKOS_ARCH values (since there is no example yet where that would be needed or useful) but such functionality could be supported in the future if needed.

All other strings in <job-name> are ignored but are allowed for informational purposes. The reason that a <job-name> string is defined in this form is that this can be used as the Jenkins job name and the Trilinos build name that shows up on CDash. This makes it very easy to define the configuration options and maintain the Jenkins build jobs. The combination <COMPILER>-<BUILD_TYPE>-<NODE_TYPE>-<KOKKOS_ACRCH> is used to define the CMake variable ATDM_JOB_NAME_KEYS_STR that is used to uniquely define a build on a particular system and to manage a system of tweaks for each of the supported builds (see below).

Some examples of <job-name> keyword sets used on various platforms include:

gnu-debug-openmp
gnu-opt-openmp
intel-debug-openmp
intel-opt-openmp
intel-debug-openmp-KNL
intel-opt-openmp-HSW
cuda-debug (<NODE_TYPE> is implicitly CUDA)
cuda-opt (<NODE_TYPE> is implicitly CUDA)
cuda-8.0-debug (<NODE_TYPE> is implicitly CUDA)
cuda-9.0-opt-Kepler37 (<NODE_TYPE> is implicitly CUDA)

The script cmake/std/atdm/load-env.sh when sourced sets some bash environment variables that are prefixed with ATDM_CONFIG_ and other standard variables. This includes setting the var ATDM_CONFIG_JOB_NAME which stores the input <job-name> which is used in other parts of the system.

The file ATDMDevEnv.cmake pulls bash environment variables set by the sourced atdm/load-env.sh script and sets up a number of CMake cache variables such as the compilers, compiler options, and sets up a number of Trilinos configuration variables (many of which are echoed to the STDOUT when running cmake). This also enables by default all of the standard TPLs used by ATDM Application codes through Trilinos and sets up locations for the include directories and libraries for each of these TPLs.

When included, the file ATDMDevEnv.cmake also disables many packages and subpackages not used for the ATDM configuration of Trilinos. This uses a so-called back-listing approach which allows one to only directly enable the packages you want to use with Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES=ON and then disable the ones you don't want. This is a much more flexible way to define a standard configuration of Trilinos that allows different sets of actual packages to be enabled based on the needs of the different ATDM application customers and Trilinos developers just needing to enable a subset of packages. But if package X does get enabled, then it will always have the same configuration options independent of any other packages that are enabled.

When ATDMDevEnv.cmake is being processed, if there is a "tweaks" file defined for a build, then it will be picked up in the CMake cache var ATDM_TWEAKS_FILES and that file will be read in using INCLUDE() to process the extra options contained within it.

Installation and usage

When including the ATDMDevEnv.cmake file (or ATDMDevEnvSettings.cmake) at configure time as described above, the cmake configure automatically sets up to install an environment script:

  <install-prefix>/<load-matching-env-sh>

where <install-prefix> and <load-matching-env-sh> are set at configure-time using:

  -D CMAKE_INSTALL_PREFIX=<install-prefix> \
  -D ATDM_INSTALLED_ENV_LOAD_SCRIPT_NAME=<load-matching-env-sh> \
  -D ATDM_TRILINOS_INSTALL_PREFIX_ENV_VAR_NAME=<trilinos-install-prefix-var-name> \

If ATDM_INSTALLED_ENV_LOAD_SCRIPT_NAME is not specified then it is given the name load_matching_env.sh by default.
If ATDM_TRILINOS_INSTALL_PREFIX_ENV_VAR_NAME is not specified then it is given the name ATDM_TRILINOS_INSTALL_PREFIX by default.

After installation with make install, a client can load the environment to use this ATDM configuration of Trilinos by running:

$ source <install-prefix>/<load-matching-env-sh>

Sourcing this file sets all of the various ATDM_CONG_ environment variables described above and also sets the environment variable <trilinos-install-prefix-var-name> to <install-prefix>.

checkin-test-atdm.sh

For those Trilinos developers comfortable with using the Trilinos/checkin-test.py script, multiple local builds and testing on a system can also be driven with the provided checkin-test-atdm.sh wrapper script. This can be used to drive a number of builds on system as:

$ cd <some_build_dir>/

$ ln -s $TRILINOS_DIR/cmake/std/atdm/checkin-test-atdm.sh .

$ ./checkin-test-atdm.sh <job-name-0> <job-name-1> ... \
  --enable-packages=<Package> --local-do-all

That will configure, build, and run tests for each specified build <job-name-0> and send a summary email when complete. All of the supported builds on the local system can be run by using all instead of <job-name-0> <job-name-1> .... See comments at the top of the script checkin-test-atdm.sh for more details.

The parallel level for building and running tests are determined by the env vars ATDM_CONFIG_BUILD_COUNT and ATDM_CONFIG_CTEST_PARALLEL_LEVEL, respectfully, as set by default for the given system by the atdm/load-env.sh script. These values can be overridden by setting the env vars ATDM_CONFIG_BUILD_COUNT_OVERRIDE and ATDM_CONFIG_CTEST_PARALLEL_LEVEL_OVERIDE, respectfully as, for example:

$ env \
  ATDM_CONFIG_BUILD_COUNT_OVERRIDE=8 \
  ATDM_CONFIG_CTEST_PARALLEL_LEVEL_OVERIDE=12 \
  ./checkin-test-atdm.sh ...

A value of ATDM_CONFIG_BUILD_COUNT_OVERRIDE=0 or less than 0 is allowed when using Ninja (i.e. ATDM_CONFIG_USE_NINJA=ON) in which case ninja will be run with non -j<N> argument, and therefore all of the non-loaded cores will be used.

Note that to run tests for a CUDA build or to run tests on platforms that must run on a compute node one will need to run these on a compute node on the system that has a GPU. On such a system one would run:

$ ./checkin-test-atdm.sh <job-name-0> <job-name-1> ... \
  --enable-packages=<Package> --configure --build \
  && \
  <command-to-run-on-compute-node> \
  ./checkin-test-atdm.sh <job-name-0> <job-name-1> ... \
  --enable-packages=<Package> --test

See Specific instructions for each system for details for how to run on the compute node for that system.

Note that one can create a local-checkin-test-defaults.py file to set defaults like:

defaults = [
  "--no-enable-fwd-packages",
  "--enable-all-packages=off",
  ]

and then run:

$ ./checkin-test-atdm.sh <job-name-0> <job-name-1> ... \
  --enable-packages=<Package> --local-do-all

However, a default local-checkin-test-defaults.py is created the first time the checkin-test-atdm.sh script is run and will set these as the defaults (after which can be modified).

Specific instructions for each system

ride/white
shiller/hansen
chama/serrano
mutrino
SEMS rhel6 environment
waterman

ride/white

Once logged on to white (on the SON) or ride (on the SRN), one can directly configure and build on the login node (being careful not to overload the node). But to run the tests, one must run on the compute nodes using the bsub command to run if using a CUDA build. For example, to configure, build and run the tests for the cuda-debug build for say MueLu on white, (after cloning Trilinos on the develop branch) one would do:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh cuda-debug

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make NP=16

$ bsub -x -Is -q rhel7F -n 16 ctest -j16

The ATDM configuration of Trilinos is set up to run on the Firestone nodes (Dual-Socket POWER8, 8 cores per socket, K80 GPUs). This confiugration will not work on the other GPU nodes currently.

Note that one can also run the same build a tests using the checkin-test-atdm.sh script as:

$ cd <some_build_dir>/
$ ln -s $TRILINOS_DIR/cmake/std/atdm/checkin-test-atdm.sh .
$ bsub -x -I -q rhel7F -n 16 \
  ./checkin-test-atdm.sh cuda-debug \
  --enable-packages=MueLu \
  --local-do-all

shiller/hansen

Once logged on to hansen (on the SON) or shiller (on the SRN), one can directly configure and build on the login node (being careful not to overload the node). But to run the tests, one must run on the compute nodes using the srun command. For example, to configure, build and run the tests for say MueLu on hansen, (after cloning Trilinos on the develop branch) one would do:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh intel-opt-openmp

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make NP=16

$ srun ctest -j16

Note that one can also run the same build a tests using the checkin-test-atdm.sh script as:

$ cd <some_build_dir>/
$ ln -s $TRILINOS_DIR/cmake/std/atdm/checkin-test-atdm.sh .
$ srun ./checkin-test-atdm.sh intel-opt-openmp \
  --enable-packages=MueLu \
  --local-do-all

chama/serrano

Once logged on to chama or serrano, one can directly configure and build on the login node (being careful not to overload the node). But to run the tests, one must run on the compute nodes using the srun command. For example, to configure, build and run the tests for say MueLu on serrano or chama, (after cloning Trilinos on the develop branch) one would do:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh intel-opt-openmp

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make NP=16

$ salloc -N1 --time=0:20:00 --account=<YOUR_WCID> ctest -j16

To get information on <YOUR_WCID> used above, there is a WC tool tab on computing.sandia.gov

To use the checkin-test-atdm.sh script, you must split running the tests from the configure and build as with:

$ cd <some_build_dir>/
$ ln -s $TRILINOS_DIR/cmake/std/atdm/checkin-test-atdm.sh .
$ ./checkin-test-atdm.sh intel-opt-openmp \
  --enable-packages=MueLu --allow-no-pull --configure --build
$ salloc -N1 --time=0:20:00 --account=<YOUR_WCID> \
  ./checkin-test-atdm.sh intel-opt-openmp \
  --enable-packages=MueLu --test

mutrino

Once logged on to mutrino, one can directly configure and build on the login node (being careful not to overload the node). But to run the tests, one must run on the compute nodes using the salloc command. For example, to configure, build and run the tests for say MueLu on mutrino, (after cloning Trilinos on the develop branch) one would:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh intel-opt-openmp

$ cmake \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make -j16

$ salloc -N 1 -p standard -J $ATDM_CONFIG_JOB_NAME ctest -j16

SEMS rhel6 environment

Once logged on to a rhel6 machine with the sems NFS, one can directly configure, build, and run tests. For example, to configure, build and run the tests for MueLu one would clone Trilinos on the develop branch and then do the following:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh intel-opt-openmp

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make NP=16

$ ctest -j16 \

waterman

Once logged on to waterman (SRN), one can directly configure and build on the login node (being careful not to overload the node). But to run the tests, one must run on the compute nodes using the bsub command to run if using a CUDA build. For example, to configure, build and run the tests for the default cuda-debug build for say MueLu (after cloning Trilinos on the develop branch) one would do:

$ cd <some_build_dir>/

$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh cuda-debug

$ cmake \
  -GNinja \
  -DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
  -DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_MueLu=ON \
  $TRILINOS_DIR

$ make NP=20

$ bsub -x -Is -n 20 ctest -j20

Note that one can also run the same build a tests using the checkin-test-atdm.sh script as:

$ cd <some_build_dir>/
$ ln -s $TRILINOS_DIR/cmake/std/atdm/checkin-test-atdm.sh .
$ bsub -x -Is -n 20 \
  ./checkin-test-atdm.sh cuda-debug \
  --enable-all-packages=off --no-enable-fwd-packages \
  --enable-packages=MueLu \
  --local-do-all

Troubleshooting configuration problems

There are situations were a particular developer on a particular system will not be able to cleanly reproduce a Trilinos configuration as described above. Some of the issues that can cause that are described here.

The first set of problems that might occur are that the version of git that is loaded by sourcing Trilinos/cmake/std/atdm/load-env.sh for a given system may conflict with the developer's global ~/.gitconfig file on that system. It may be that an older or newer version of git is loaded by the script (i.e. <atdm-loaded-git>) than the git version that the developer has been using on the system (i.e. <developer-git>) and therefore some of the settings in the developer's ~/.gitconfig file may not be compatible with the different version of git. One approach to address this is run module list to see the version of git that is loaded by this script and then to swap out that version of git for the developer's regular version of git using module swap <atdm-loaded-git> <developer-git>. Or, the developer can just call export PATH=<path-to-developers--git>/bin:$PATH after sourcing Trilinos/cmake/std/atdm/load-env.sh to select the developer's regular version of git. The git commands that are used by TriBITS, Trilinos, and the ATDM Trilinos configuration and testing scripts should work with just about any version of git 2.0+. Another approach would be for the user to (temporarily) edit their ~/.gitconfig file to address the problems.

Directory structure and contents

This base directory:

  cmake/std/atdm/

contains the following files:

ATDMDevEnvSettings.cmake: Reads vars out of the env (loaded with load-env.sh) to set compilers and other options for the Trilinos build. It also default enables all of the TPLs used in ATDM configurations of Trilinos. However, this file does not include ATDMDisables.cmake. Therefore, this file can be used to set up builds of Trilinos that enable arbitrary sets of packages.
ATDMDisables.cmake: Disables a bunch of Trilinos packages and subpackages not used by ATDM application customers. This file gets included automatically in ATDMDevEnv.cmake (so you don't need to list it in local configures of Trilinos). But this file is also included in the outer ctest -S driver script code for ATDM builds of Trilinos which is needed for correct package-by-package testing of Trilinos.
ATDMDevEnv.cmake: Includes ATDMDevEnvSettings.cmake and ATDMDisables.cmake.
checkin-test-atdm.sh: Uses the Trilinos/checkin-test.py script to drive builds and tests on the given platform. (See comments in the top of the script for instructions.)

Each supported ATDM system <system-name> has its own sub-directory with the contents:

  <system-name>/
    environment.sh  # Load env for the given system based on $ATDM_CONFIG_JOB_NAME keys
    all_supported_builds.sh  # [Optional] List of all supported builds
    tweaks/
       <COMPILER0>-<BUILD_TYPE0>-<NODE_TYPE0>.cmake  # [Optional]
       <COMPILER1>-<BUILD_TYPE1>-<NODE_TYPE1>.cmake  # [Optional]
       ...

The optional file <system-name>/all_supported_builds.sh contains a list of all of the supported builds on the system. This sets the environment variable ATDM_CONFIG_ALL_SUPPORTED_BUILDS as:

  export ATDM_CONFIG_ALL_SUPPORTED_BUILDS="gnu-debug-openmp gnu-opt-openmp ..."

This is used in the checkin-test-atdm.sh script to run all of the builds for a system with checkin-test-atdm.sh all [other options].

The files in the cmake/std/atdm/<system-name>/tweaks/ directory contain special settings for specific builds for a specific system. Typically, this file contains (temporary) disables for tests for that given build. When a configure is performed, the variable ATDM_JOB_NAME_KEYS_STR set to <COMPILER>-<BUILD_TYPE>-<NODE_TYPE>-<KOKKOS_ARCH> (printed to STDOUT) is used to define a default file name:

  Trilinos/cmake/std/atdm/<system-name>/tweaks/$ATDM_JOB_NAME_KEYS_STR.cmake

If that file exists, then it is set as the default for the cmake cache variable ATDM_TWEAKS_FILES (prints to STDOUT) and that file is included and its options are read.

Disabling failing tests

There are situations where specific tests must be disabled on certain platforms for certain builds or based on other criteria (see sub-process Temporarily disable the failing code or test). There are various ways to disable tests with the Trilinos TriBITS/CMake-based build and test system. Tests can be disabled in the CMakeLists.txt files that define the tests themselves using various logic. But the way to selectively disable tests for the ATDM Trilinos builds that will be described here will be to only modify files under the Trilinos/cmake/std/atdm/ directory. This will be done by setting the CMake cache variable <full-test-name>_DISABLE=ON for each test to be disabled where <full-test-name> is the full test name. For example, to disable the test MueLu_UnitTestsTpetra_MPI_4, one would set the CMake cache variable MueLu_UnitTestsTpetra_MPI_4_DISABLE=ON. The TriBITS/CMake configure system will then disable the test and print the following line during configuration (when Trilinos_TRACE_ADD_TEST=ON is also set):

-- MueLu_UnitTestsTpetra_MPI_4: NOT added test because MueLu_UnitTestsTpetra_MPI_4_DISABLE='ON'!

The CMake function ATDM_SET_ENABLE() is provided in order to set the disable such as with:

ATDM_SET_ENABLE(MueLu_UnitTestsTpetra_MPI_4_DISABLE ON)

Using this function will result in the CMake cache variable <full-test-name>_DISABLE to get set to ON by default and will print the disable to the CMake STDOUT when the ATDM_SET_ENABLE() is run, such as:

-- Setting default MueLu_UnitTestsTpetra_MPI_4_DISABLE=ON

This approach also allows a user to enable the test by adding -D<full-test-name>_DISABLE=OFF to the configure line (which overrides the default ON).

However, before any tests are disabled, there must be a Trilinos GitHub issue addressing the failing test(s) and the GitHub issue number (e.g. #2839) must put into a comment above the ATDM_SET_ENABLE() statement and the issue number must be added to the git commit message (see Create a Trilinos GitHub issue for the failure).

The best file to add the ATDM_SET_ENABLE(<full-test-name>_DISABLE ON) statement to based on different situations is described in the following sub-sections:

Disable a test for a specific build on a specific platform
Disable a test for several or all builds on a specific platform
Disable a test for builds on all platforms

Disable a test for a specific build on a specific platform

In order to disable a test for a single build on single platform, one will want to put the ATDM_SET_ENABLE() statement into the tweaks file for that build and platform:

  Trilinos/cmake/std/atdm/<system-name>/tweaks/<ATDM_JOB_NAME_KEYS_STR>.cmake

The tweak file being looked for is printed out in the CMake configure output as the line:

-- ATDM_TWEAKS_FILES='.../Trilinos/cmake/std/atdm/<system-name>/tweaks/<ATDM_JOB_NAME_KEYS_STR>.cmake'

For example, for the intel-debug-openmp-KNL build on 'mutrino', the printout would be:

-- ATDM_TWEAKS_FILES='.../Trilinos/cmake/std/atdm/mutrino/tweaks/INTEL-DEBUG-OPENMP-KNL.cmake'

For example, Trilinos commit 73ae19cf0c shows the disable of the test:

# Disable test that times out for some unkown reason (#2925)
ATDM_SET_ENABLE(Stratimikos_test_aztecoo_thyra_driver_MPI_1_DISABLE ON)

in both the files cmake/std/atdm/shiller/tweaks/GNU-DEBUG-SERIAL.cmake and cmake/std/atdm/shiller/tweaks/GNU-RELEASE-SERIAL.cmake (before -HSW was added to the names).

NOTE: Adding a comment with the Trilinos GitHub Issue ID (#2925 in this example) is critical for tractability to remind why the test was disabled and where to find the disable to remove it later.

To avoid duplicate ATDM_SET_ENABLE() statements, one can use the approach of creating a single *.cmake that is included in the different tweak files as described below.

Disable a test for several or all builds on a specific platform

It is often the case that a test needs to be disabled for several (or all) builds for a given platform. An efficient way to do this is to create a new *.cmake file that contains the ATDM_SET_ENABLE() statements and then include that new file in all of the tweaks files on that system where the tests should be disabled.

For example, the Trilinos commit 3450efd421 shows how a set of tests were disabled for all of the CUDA builds on the system ride through the creation of the file:

  Trilinos/cmake/std/atdm/ride/tweaks/CUDA_COMMON_TWEAKS.cmake

and then the inclusion of that file in the specific tweak files for each CUDA build:

  Trilinos/cmake/std/atdm/ride/tweaks/CUDA-DEBUG-CUDA.cmake
  Trilinos/cmake/std/atdm/ride/tweaks/CUDA-RELEASE-CUDA.cmake

(before -POWER8-KEPLER37 was added to the names) using the inserted CMake statement:

INCLUDE("${CMAKE_CURRENT_LIST_DIR}/CUDA_COMMON_TWEAKS.cmake")

An example of using a *.cmake file to disable the same set of tests in all of the builds for a given system is shown in Trilinos commit 33a933b004. This example shows the creation of the file:

  Trilinos/cmake/std/atdm/ride/tweaks/ALL_COMMON_TWEAKS.cmake

and then the inclusion of that file in all of the specific tweaks files on 'ride' with the statement:

INCLUDE("${CMAKE_CURRENT_LIST_DIR}/ALL_COMMON_TWEAKS.cmake")

in each of those files.

Disable a test for builds on all platforms

There are rare cases where a test (or a set of tests) will need to be disabled for all or a subset of builds across all systems. To do that using the above-described approaches would require touching files in every cmake/std/atdm/<system-name>/tweaks/ directory. In rare cases like this, one can accomplish this by adding a (conditional) ATDM_SET_ENABLE() statement for each test disable directly to the file:

  Trilinos/cmake/std/atdm/ATDMDevEnvSettings.cmake

For example, Trilinos commit 5e52db03ff added the CMake code:

# Disable test that fails for all openmp builds (#3035)
IF (ATDM_USE_OPENMP)
  ATDM_SET_ENABLE(MueLu_UnitTestsTpetra_MPI_4_DISABLE ON)
ENDIF()

to the file ATDMDevEnvSettings.cmake to disable the test MueLu_UnitTestsTpetra_MPI_4 for all OpenMP builds across all platforms. (Note that that disable was later removed in Trilinos commit 62fa6663a6 after the test was fixed.)

Specific systems supported

The specific cmake/std/atdm/<system-name>/ sub-directories and the systems they support are:

chama/: Supports SNL HPC machine chama.
mutrino/: Supports SNL HPC machine mutrino.
rhel6/: RHEL6 systems with the SEMS NFS environment
ride/: Supports GNU and CUDA builds on both the SRN machine ride and the mirror SON machine white.
serrano/: Supports SNL HPC machine serrano.
shiller/: Supports GNU, Intel, and CUDA builds on both the SRN machine shiller and the mirror SON machine hansen.
wateman/: Supports GNU and CUDA builds on the SRN machine waterman.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

Local ATDM builds of Trilinos

Quick-start

Installation and usage

checkin-test-atdm.sh

Specific instructions for each system

ride/white

shiller/hansen

chama/serrano

mutrino

SEMS rhel6 environment

waterman

Troubleshooting configuration problems

Directory structure and contents

Disabling failing tests

Disable a test for a specific build on a specific platform

Disable a test for several or all builds on a specific platform

Disable a test for builds on all platforms

Specific systems supported

Files

README.md

Latest commit

History

README.md

File metadata and controls

Local ATDM builds of Trilinos

Quick-start

Installation and usage

checkin-test-atdm.sh

Specific instructions for each system

ride/white

shiller/hansen

chama/serrano

mutrino

SEMS rhel6 environment

waterman

Troubleshooting configuration problems

Directory structure and contents

Disabling failing tests

Disable a test for a specific build on a specific platform

Disable a test for several or all builds on a specific platform

Disable a test for builds on all platforms

Specific systems supported