Closed shahzebsiddiqui closed 1 year ago
@wspear can you help with sending a template or list of packages we need to test for this stack
@shahzebsiddiqui I should be able to get a PR together for this tomorrow. I've created a very basic (possibly not very robust) script that takes the intersection of spack find -x
andspack test list
. This is what it turns out for e4s/22.11%gcc, which I'll use to generate the new buildtests unless you have input to the contrary.
aml
amrex
arborx
bolt
caliper
fortrilinos
gasnet
ginkgo
gptune
heffte
hpctoolkit
kokkos
legion
mfem
omega-h
openpmd-api
papyrus
parallel-netcdf
parsec
pumi
py-h5py
py-libensemble
py-petsc4py
py-warpx
qthreads
slate
slepc
sundials
superlu
tasmanian
tau
upcxx
vtk-m
i also posted an issue to spack for feature spack test list -x
and spack test list -X
to help address this use-case https://github.com/spack/spack/issues/37025
This is the template I'm considering for these tests:
#This buildtest was generated from spack-test-22.11-template.yaml
buildspecs:
{package}_spack-test_22.11:
type: spack
executor: perlmutter.slurm.regular
description: Run spack test for {package} from e4s/22.11 gcc stack
tags: [e4s]
sbatch: ["-t 30", "-N 1", "-G 1", "-A m3503_g", "-C gpu"]
tags: e4s
pre_cmds: |
module load e4s/22.11
spack env activate gcc
spack load --first cmake
spack load --first {package}
spack:
root: /global/common/software/spackecp/perlmutter/e4s-22.11/default/spack
verify_spack: false
test:
run:
specs: ['{package}']
results:
option: '-l'
specs: ['{package}']
maintainers:
- shahzebsiddiqui
- wspear
An issue to consider: there are some duplicate packages in these e4s deployments. When more than one package of the same name is installed I'm not sure how it will behave with only the 'first' found version loaded. Alternatives are to not load the package at all and consider requiring pre-loading the package to be an issue with the test or to do a more advanced extraction of installed specs and create separate buildspecs that specify the hash for each test to be run.
PR is here. Thanks to the template, making any changes across all the new tests will be quick. https://software.nersc.gov/NERSC/buildtest-nersc/-/merge_requests/164
list of available spack environments
Here is list of available tests
available tests in cuda environments
available tests in gcc environment