-
Notifications
You must be signed in to change notification settings - Fork 87
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
WIP: Tag jobs by required runner capabilities #1394
Closed
Closed
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
ginkgo-bot
added
reg:build
This is related to the build system.
reg:testing
This is related to testing.
reg:ci-cd
This is related to the continuous integration system.
reg:documentation
This is related to documentation.
reg:example
This is related to the examples.
reg:benchmarking
This is related to benchmarking.
type:solver
This is related to the solvers
type:preconditioner
This is related to the preconditioners
type:matrix-format
This is related to the Matrix formats
type:reordering
This is related to the matrix(LinOp) reordering
type:multigrid
This is related to multigrid
mod:all
This touches all Ginkgo modules.
labels
Aug 20, 2023
MarcelKoch
force-pushed
the
ctest-resources
branch
from
August 21, 2023 00:48
c796297
to
fbec06b
Compare
otherwise, the default stream is used in some places, e.g. initializing cublas. But it is not clear with which device the default stream is associated. Thus, this now sets the device id correctly for the new stream
this is necessary, since some test call the kernels directly and not through the executor. In this case, the setting of the device id by the executor is skipped, which leads to these kernel not run.
Co-authored-by: Tobias Ribizel <[email protected]>
Co-authored-by: Tobias Ribizel <[email protected]>
- remove test file - small documentation - more verbose device id output Co-authored-by: Tobias Ribizel <[email protected]>
Co-authored-by: Marcel Koch <[email protected]>
Co-authored-by: Tobias Ribizel <[email protected]>
- cmake documentation - take omp num thread into account for resource file Co-authored-by: Yu-Hsiang M. Tsai <[email protected]>
upsj
force-pushed
the
gitlab_capability_tags
branch
from
August 26, 2023 21:23
cd00a74
to
286b028
Compare
upsj
force-pushed
the
gitlab_capability_tags
branch
from
August 26, 2023 21:24
286b028
to
2b26e7e
Compare
upsj
force-pushed
the
ctest-resources
branch
2 times, most recently
from
September 1, 2023 14:47
0799a12
to
4c2defa
Compare
Merged
I'll redo this properly in the future |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1:ST:WIP
This PR is a work in progress. Not ready for review.
mod:all
This touches all Ginkgo modules.
reg:benchmarking
This is related to benchmarking.
reg:build
This is related to the build system.
reg:ci-cd
This is related to the continuous integration system.
reg:documentation
This is related to documentation.
reg:example
This is related to the examples.
reg:testing
This is related to testing.
type:matrix-format
This is related to the Matrix formats
type:multigrid
This is related to multigrid
type:preconditioner
This is related to the preconditioners
type:reordering
This is related to the matrix(LinOp) reordering
type:solver
This is related to the solvers
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.
Right now, we use tags like
amdci
andhoreka
to determine where to run our tests. It would be more scalable if instead we just listed which capabilities a runner has in its tags (nvidia-gpu
,nvidia-multi-gpu
,amd-gpu
,amd-multi-gpu
andcpu
come to mind). That way, we can move to other platforms much more seamlessly if necessary.Also, it seems that none of our AMD tests running on
nla1
? We should change that.The branch is a bit messy since it is based on a rebased
ctest-resources
branch, only the last commit is interesting.This PR is not final yet, I want to use it to collect necessary changes to enable running on apptainer FTP/Horeka.