New system class: perlmutter

[slabasan]

Description

Depends on #1134

Add description for perlmutter

benchpark system init --dest=perlmutter-system lbnl-perlmutter timeout=30 queue={debug,regular} constraint=cpu

timeout in minutes

• Add/modify systems/all_hardware_descriptions/hardware_name/hardware_description.yaml which will appear in the docs catalogue
• Update for Spack 1.0
• Test stream -- builds and runs
• Test stream caliper=mpi,time -- builds and runs
• Test amg2023 -- builds and runs
• WIP Test kripke+cuda -- builds, run fails with MPIDI_CRAY_init: GPU_SUPPORT_ENABLED is requested, but GTL library is not linked. Perlmutter docs says: When building an application that uses CUDA-aware MPI, you must set the accelerator target to nvidia80 via the compile flag -target-accel=nvidia80 or the environment variable CRAY_ACCEL_TARGET. Run succeeds by manually editing execute_experiment and adding MPICH_GPU_SUPPORT_ENABLED=0 or MPICH_GPU_SUPPORT_ENABLED=1 to the beginning of the srun command.
• @stephanielam3211 Test pingpong
• Possibly in a later PR: find cusolver on Perlmutter. Test amg2023+cuda

Build output:

wkp/kripke-benchmark/perlmutter-system/workspace/software/spack/kripke/._ramble/v6seegbgfkxr34nof4j3iu4bxcg3n2qv/.spack/kripke/spack-build-out.txt.gz 

spack env activate stream-benchmark/perlmutter-system/workspace/software/spack/stream/
spack env activate -d stream-benchmark/perlmutter-system/workspace/software/spack/stream/
spack env list
spack env status
spack concretize -f -U
module load cmake/3.30.2
spack external find cmake
spack concretize -f -U
spack install -j1000 --keep-stage
spack config blame packages
spack config get
spack config get packages

Debugging:

spack cd -s kripke # activate build, so we can see build logs

Adding/modifying a system (docs: Adding a System)

• Add/modify systems/system_name/system.py file
• Add/modify systems/all_hardware_descriptions/hardware_name/hardware_description.yaml which will appear in the docs catalogue

[stephanielam3211]

==> Error: failed to concretize stream@5.10-caliper+caliper, caliper@master+adiaklibdwlibunwind+mpi~papi for the following reasons:

1. Only external, or concrete, compilers are allowed for the fortran language
2. Only external, or concrete, compilers are allowed for the cxx language
3. 3. Only external, or concrete, compilers are allowed for the c language. You could consider setting concretizer:unify to when_possible or false to allow multiple versions of some packages.

(gcc error above)

[slabasan]

Replaces #731

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.47%. Comparing base (16e65fa) to head (7931ed3).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1086      +/-   ##
===========================================
+ Coverage    63.29%   63.47%   +0.17%     
===========================================
  Files           45       45              
  Lines         3395     3395              
  Branches       261      261              
===========================================
+ Hits          2149     2155       +6     
+ Misses        1236     1231       -5     
+ Partials        10        9       -1     

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.