-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated CI driving scripts. #93
Conversation
casparvl
commented
Oct 9, 2023
- Take config out of the scripts that drive the CI.
- Add config for aws and vega.
- Add documentation in README on how to do regular runs on one's own system, reusing this setup of scripts/config.
… the CI. Add config for aws and vega. Add documentation in README on how to do regular runs on one's own system, reusing this setup of scripts/config
…ever we load in the prerun_cmds in the ReFrame config file for that system
…time using the EESSI_VERSION environment variable. This can then later be used in CI as soon as we have a new release....
…ed to initialize the desired EESSI version
… runs on a host that doesn't have libxml2 and libxslt
…figs. We still _want_ them to be configurable though
…nment based on EESSI_VERSION
… Alter node names for Magic Castle on AWS
I've created https://github.com/EESSI/test-suite/pull/93/files#diff-dd3fbcffcf747567780655d9a5c7219d5787ada95069bf20a65c7ac2f804a1c2 in a way that it works now. We probably want to change that to use the |
@@ -0,0 +1,7 @@ | |||
# Configurable items | |||
REFRAME_ARGS="--tag CI --tag 1_node|2_nodes" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are not enough resources on aws_mc to do the 2_nodes tests.
…s to be in a released branch, then we can point the EESSI_TESTSUITE_URL and EESSI_TESTSUITE_BRANCH to this