Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
.github/scripts/install_and_test.shscript is executed only on the private runners, it installs, compiles and tests struphy. It can be executed manually too and should work on Raven/Viper/TOK/PitagoraTo simplify the installation on the clusters, I've added the following bash files in
setup/:modules.pitagora.shmodules.raven.shmodules.tok.shmodules.viper.shmodules.shThe
modules.MACHINEcontain the variablesMODULES_INTELandMODULES_GCCwhich lists the modules needed for intel/gcc on the current machine.The
modules.shdetects which machine we are on, and helps you load or show the modules needed.So for example, if you want to load the GCC modules (which is default), you just type:
To load the intel modules, you type: