Developer Guide

CHAI shares its Uberenv workflow with other projects. The documentation is therefore `shared`_.

This page will provides some CHAI specific examples to illustrate the workflow described in the documentation.

Machine specific configuration

$ ls -c1 scripts/uberenv/spack_configs

CHAI has been configured for toss_3_x86_64_ib and other systems.

Vetted specs

$ ls -c1 .gitlab/*jobs.yml

CI contains jobs for quartz.

$ git grep -h "SPEC" .gitlab/quartz-jobs.yml | grep "gcc"
    SPEC: "%gcc@4.9.3"
    SPEC: "%gcc@6.1.0"
    SPEC: "%gcc@7.1.0"
    SPEC: "%gcc@7.3.0"
    SPEC: "%gcc@8.1.0"

We now have a list of the specs vetted on quartz/toss_3_x86_64_ib.


In practice, one should check if the job is not allowed to fail, or even deactivated.

MacOS case

In CHAI, the Spack configuration for MacOS contains the default compilers depending on the OS version (compilers.yaml), and a commented section to illustrate how to add CMake as an external package. You may install CMake with homebrew, for example.

Using Uberenv to generate the host-config file

We have seen that we can safely use gcc@8.1.0 on quartz. Let us ask for the default configuration first, and then ask for RAJA support and link to develop version of RAJA:

$ python scripts/uberenv/ --spec="%clang@9.0.0"
$ python scripts/uberenv/ --spec="%clang@9.0.0+raja ^raja@develop"

Each will generate a CMake cache file, e.g.:


Using host-config files to build CHAI

$ mkdir build && cd build
$ cmake -C <path_to>/<host-config>.cmake ..
$ cmake --build -j .
$ ctest --output-on-failure -T test

It is also possible to use this configuration with the CI script outside of CI:

$ HOST_CONFIG=<path_to>/<host-config>.cmake scripts/gitlab/

Testing new dependencies versions

CHAI depends on Umpire, and optionally CHAI. Testing with newer versions of both is made straightforward with Uberenv and Spack:

  • $ python scripts/uberenv/ --spec=%clang@9.0.0 ^umpire@develop
  • $ python scripts/uberenv/ --spec=%clang@9.0.0+raja ^raja@develop

Those commands will install respectively umpire@develop and raja@develop locally, and generate host-config files with the corresponding paths.

Again, the CI script can be used directly to install, build and test in one command:

$ SPEC="%clang@9.0.0 ^umpire@develop" scripts/gitlab/