local-gpu-executor repects CUDA_VISIBLE_DEVICES when set #6218
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
|
I don't know why this PR shows so many changes. |
bentsherman
force-pushed
the
local-gpu-executor
branch
from
d1f1a8a to
ec6a888
Compare
|
Incorporated into #5850 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In #5850, if
nextflowis run withCUDA_VISIBLE_DEVICESenvironment variable set before hand, the gpuIDs inCUDA_VISIBLE_DEVICESare ignored when building theavailIdsMap.This PR proposes a fix.
When
executor.gpusis greater than number of devices specified inCUDA_VISIBLE_DEVICES, an error is thrown.If
CUDA_VISIBLE_DEVICESis not set, then the0..ngpuIDs are used to buildavailIdsas before.