RAJA Performance Suite Continuous Integration (CI) Testing

The RAJA Performance Suite project uses the same continuous integration tools as the RAJA project, namely GitHub Actions and GitLab CI in the Livermore Computing Collaboration Zone (LC CZ). Please see RAJA Continuous Integration Testing for more information.

The RAJA Performance Suite project includes files that support GitLab and GitHub Actions CI testing that are specific to the project. These file are similar to those in the RAJA project and play the same roles and follow the same structure as in the RAJA project. Such files are described in RAJA Continuous Integration Testing.

An important difference to note between RAJA Performance Suite GitLab CI and RAJA GitLab CI is that the RAJA Performance Suite inherits most of its support from its RAJA submodule. As a result, submodules that support RAJA GitLab CI, such as Uberenv and RADIUSS Spack Configs, do not appear in the RAJA Performance Suite repository. Instead, the RAJAPerf/scripts/gitlab/build_and_test.sh script invokes the uberenv.py script in the RAJA submodule to drive Spack and the RAJAPerf/.uberenv_config.json file points to the RADIUSS Spack Configs content in the RAJA submodule:

{
"package_name" : "raja-perf",
"package_version" : "develop",
"package_final_phase" : "initconfig",
"package_source_dir" : "../..",
"spack_url": "https://github.com/spack/spack.git",
"spack_branch": "v1.1.1",
"spack_configs_path": "tpl/RAJA/scripts/radiuss-spack-configs",
"spack_packages_path": "tpl/RAJA/scripts/radiuss-spack-configs/spack_repo/llnl_radiuss/packages",
"spack_setup_clingo": false
}

Like RAJA, the RAJA Performance Suite Spack package is maintained in the Spack Packages project on GitHub.

Continuous Integration (CI) Testing Maintenance Tasks

Tasks for maintaining continuous integration in the RAJA Performance Suite project are similar to those for RAJA. Please see RAJA Continuous Integration Testing Maintenance Tasks for details.