UENV CI #1053
Open
UENV CI #1053
Conversation
This file contains 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
simonpintarelli
force-pushed
the
uenv-ci
branch
from
3c643d9 to
2c44d96
Compare
simonpintarelli
force-pushed
the
uenv-ci
branch
from
2c44d96 to
8ea90c0
Compare
|
cscs-ci run default |
|
cscs-ci run default |
|
cscs-ci run default |
|
cscs-ci run default |
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.
Since the container CE fails on a second MPI_Init (ctest calls all test in the same srun) I suggest to use uenv for the CI.
stages:
The build stage previously built a container based on the baseimage and then pushed it to jfrog (incl the build directory). Now we store the build directory as artifact and unpack it before running the tests. Therefore I think it's around the same cost.
Note I disabled auto trigger for cscs ci, it must be run manually now. I think otherwise it would waste a lot of NH.