Thomas Röblitz
Thomas Röblitz
WORK IN PROGRESS Eventually, this is aimed at adding PyTorch/2.1.2 with CUDA/12.1.1. However, building it may not work out of the box, so this is for documenting the progress, issues...
requires: * #720 Attempt to add cuDNN which is a dependency of other packages such as TensorFlow and PyTorch. Major additions/changes: - `scripts/gpu_support/nvidia/install_cuda_and_libraries.sh` with `scripts/gpu_support/nvidia/eessi-2023.06-cuda-and-libraries.yml` - script to install `CUDA`...
In https://github.com/NorESSI/software-layer/pull/323 building failed for `aarch64/generic`. The build job was run on a compute node with `ThunderX2` CPU. `kokkos_arch` was not explicitly set. If `kokkos_arch` is not explicitly, the LAMMPS...
This improves the usability of `bot/inspect.sh` / fixes a bug. If one ran the script from another directory as the working directory of a bot job (or the main directory...
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...
The `bot/build.sh` runs `eessi_container.sh` twice and each run results in a tarball containing the temporary folder. If a job runs on a machine where this temporary folder is not cleaned...
Ran into the issue in https://github.com/NorESSI/software-layer/pull/301 which tests the changes implemented in https://github.com/EESSI/software-layer/pull/494 Particularly, the https://github.com/NorESSI/software-layer/pull/301 includes several comments which contain the string `from-pr` in addition to the option `from-pr`...
The current `EESSI-pilot-install-software.sh` works in two main steps: 1. Building (missing) software packages. 2. Creating a single tarball for new files added through step 1. This is challenging for larger...
A script `bot-create-tarball.sh` could handle all environment settings etc and would thereby make the build script of the EESSI bot (`eessi-bot-build.slurm`) simpler. See original post by @boegel in https://github.com/EESSI/eessi-bot-software-layer/pull/10#discussion_r894927012