A few module generation pecularities

[mart...@gmail.com]

I am seeing a few issues with Lmod modules generation that I am not sure where they are coming from.

The first is the function of the blacklisting and whitelisting. In our modules.yaml, I have:

    blacklist_implicits: true
    whitelist:
      - intel-mpi

       ...

But, when I explicitly build a package, it's still saying that it's blacklisted as implicit. Why would Spack think the package (e.g lammps below) that is explicitly installed is implicit?

 
$ spack -d install lammps +user-colvars+user-plumed+replica target=nehalem

...

==> [2021-05-05-10:11:57.311734]     BLACKLISTED_AS_IMPLICIT : lammps@20210310%g...@8.3.0 ... arch=linux-centos7-nehalem/epn4b2a
==> [2021-05-05-10:11:57.312301]     NOT WRITING: lammps@20210310%g...@8.3.0 ... arch=linux-centos7-nehalem/epn4b2a [BLACKLISTED]

Secondly, for whatever reason, Spack is putting the module file to its directory, $SPACK/share/spack/modules. I am not sure how it figures that out since in our config.yaml we only have:

  module_roots:
    lmod: /uufs/chpc.utah.edu/sys/modulefiles/spack

and e.g. for the lammps Spack does do:

==> [2021-05-05-10:11:57.341927]     WRITE: lammps@20210310%g...@8.3.0 ... arch=linux-centos7-nehalem/epn4b2a [/uufs/chpc.utah.edu/sys/installdir/spack/0.16.1/share/spack/modules/linux-centos7-nehalem/lammps-20210310-gcc-8.3.0-epn4b2a]

Any thoughts on this would be appreciated.

[Groner, Rob]

For the second part, try:  spack config blame config  

and see where it says that the module_roots is set to and coming from. 

---

From: sp...@googlegroups.com <sp...@googlegroups.com> on behalf of mart...@gmail.com <mart...@gmail.com>
Sent: Wednesday, May 5, 2021 1:16 PM
To: Spack <sp...@googlegroups.com>
Subject: [spack] A few module generation pecularities

 

--
You received this message because you are subscribed to the Google Groups "Spack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spack+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/spack/5b3fe1aa-17a3-4b2b-ae95-20785f5180a5n%40googlegroups.com.

[mart...@gmail.com]

Good catch, thanks. I did not realize that all the hierarchy in the config files is being read so I also had the "default", /uufs/chpc.utah.edu/sys/installdir/spack/0.16.1/etc/spack/defaults/config.yaml, in the way. And haven't used the "spack config blame" before, that's very useful.

[Groner, Rob]

Heh, I'm pretty sure I came to discover "spack config blame" in the same way...someone pointing me to it when I couldn't understand what was happening.  Glad I could pay it forward.  

Rob

---

From: sp...@googlegroups.com <sp...@googlegroups.com> on behalf of mart...@gmail.com <mart...@gmail.com>

Sent: Wednesday, May 5, 2021 1:36 PM
To: Spack <sp...@googlegroups.com>
Subject: Re: [spack] A few module generation pecularities

 

To view this discussion on the web visit https://groups.google.com/d/msgid/spack/e89092d6-64e8-4a75-b7f4-710233a1b28cn%40googlegroups.com.