NERSC / buildtest-nersc

MIT License
8 stars 16 forks source link

[Bug]: false positive on e4s_22.05_spack_load #166

Closed shahzebsiddiqui closed 1 year ago

shahzebsiddiqui commented 1 year ago

CDASH Build

https://my.cdash.org/test/75772794

Link to buildspec file

https://github.com/buildtesters/buildtest-nersc/blob/devel/buildspecs/apps/e4s/22.05/developer_workflow.yml

Please describe the issue?

we are not loading the environment which is causing issue with spack load command https://github.com/buildtesters/buildtest-nersc/blob/58bca5751fb0f191d2706a5571f711f868c74561/buildspecs/apps/e4s/22.05/developer_workflow.yml#L53

Relevant log output

_______________________________________________________________________________________________________
     The Extreme-Scale Scientific Software Stack (E4S) is accessible via the
Spack package manager.
     In order to access the production stack, you will need to load a spack
environment. Here are some tips to get started:

     'spack env list' - List all spack environments
     'spack env activate -V gcc' - Activate spack environment 'gcc' without
spack view
     'spack env activate gcc' - Activate spack environment 'gcc' with spack
view
     'spack env status' - Display which spack environment is activated
     'spack load amrex' - Load spack package 'amrex' into user environment
     For additional support, please refer to the following references:

       NERSC E4S Documentation: https://docs.nersc.gov/applications/e4s/
       E4S Documentation: https://e4s.readthedocs.io
       Spack Documentation: https://spack.readthedocs.io/en/latest/
       Spack Slack: https://spackpm.slack.com
______________________________________________________________________________________________________

==> Error: Spec 'hdf5@1.10.7%gcc@11.2.0' matches no installed packages.
/global/common/software/nersc/pm-2022q3/sw/python/3.9-anaconda-2021.11/bin/h5cc: line 388: x86_64-conda-linux-gnu-cc: command not found
==> Error: Spec 'hdf5@1.10.7%gcc@11.2.0' matches no installed packages.
shahzebsiddiqui commented 1 year ago

we need to mimic the test example shown in our docs https://docs.nersc.gov/applications/e4s/spack/#loading-spack-packages-into-your-user-environment so i think the key is running spack env activate -V gcc.

@jscook2345 can you please take a look at this issue, it should be relatively easy fix.

shahzebsiddiqui commented 1 year ago

this was addressed in MR https://software.nersc.gov/NERSC/buildtest-nersc/-/merge_requests/162