-
-
Notifications
You must be signed in to change notification settings - Fork 27
Sync up unique cache paths for Singularity images with cwltool #433
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
Open
adamnovak
wants to merge
2
commits into
common-workflow-language:main
Choose a base branch
from
adamnovak:robust-sif-cache
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
| """Tests for classes for docker-extract.""" | ||
|
|
||
| from cwl_utils.image_puller import SingularityImagePuller | ||
| from cwl_utils.singularity import get_version as get_singularity_version | ||
| from cwl_utils.singularity import is_version_2_6 as is_singularity_version_2_6 | ||
| from cwl_utils.singularity import ( | ||
| is_version_3_or_newer as is_singularity_version_3_or_newer, | ||
| ) | ||
|
|
||
| from .util import needs_singularity | ||
|
|
||
|
|
||
| @needs_singularity | ||
| class TestSingularityImagePuller: | ||
| """Tests for SingularityImagePuller.""" | ||
|
|
||
| def test_get_image_name_matches_cwltool(self) -> None: | ||
| """Make sure image names generated match those expected by cwltool.""" | ||
| if is_singularity_version_2_6(): | ||
| suffix = ".img" | ||
| elif is_singularity_version_3_or_newer(): | ||
| suffix = ".sif" | ||
| else: | ||
| raise Exception( | ||
| f"Don't know how to handle this version of singularity: {get_singularity_version()}." | ||
| ) | ||
|
|
||
| def get_name(s: str) -> str: | ||
| return SingularityImagePuller(s, None, "", False).get_image_name() | ||
|
|
||
| assert get_name("some_name/repo:123") == f"some___name_s_repo:123{suffix}" | ||
| assert get_name("some/name_repo:123") == f"some_s_name___repo:123{suffix}" |
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.
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.
Hey @adamnovak ! Thank you for this and the linked PR. I worry that this will cause existing stored images to be ignored. Any idea on how we can diverge less from the previously naming scheme?
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.
One problem that's being solved here is name collisions: it's possible with the previous naming scheme to have two distinct images (mostly pairs like
a/b_canda_b/c) share a cache key.The obvious way to re-use existing cached images would be to look and see if the files already exist under the old scheme. Maybe that's OK even if there were possible collisions, since we won't create any new collisions and if people have images cached they must have been working.
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.
yes, please and thank you