software-layer
software-layer copied to clipboard
Software layer of the EESSI project
Also edited the umask for various scenarios: - for host wide installations, installations are world readable (umask 022) - for project installations, installations are also group writable (umask 002) -...
We are interested in verifying if the ReFrame tests run are using the updated GROMACS build. We probably have to inspect the log files on the build cluster for this.
Use case for this is that we want to test software additions to a CernVM-FS repository. Typically we would first run `eessi_container.sh` with `--access rw` to make the repository writable...
[Currently](https://github.com/EESSI/software-layer/blob/4afaecbcf387dd4a4cea45a546ed1de79f3f6b7c/test_suite.sh#L178), the test step runs all tests tagged with `-t CI -t '1_node|2_nodes'`. To save time, we'll limit it to only running the OSU tests for now [through this PR](https://github.com/EESSI/software-layer/pull/571)....
``` 2 out of 113 required modules missing: * KaHIP/3.16-gompi-2023a (KaHIP-3.16-gompi-2023a.eb) * OpenFOAM/v2312-foss-2023a (OpenFOAM-v2312-foss-2023a.eb) ```
With help from @casparvl, I've added the following to `/project/def-users/bot/shared/host-injections/2023.06/.lmod/SitePackage.lua` on our AWS build cluster, which will be picked up by the bot for builds relying on `libfabric`: ``` require("strict")...
We're configuring GROMACS