-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unittest images #36
Closed
Closed
Unittest images #36
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
Looks through all directories for unittest.yml files. It assumes there is a Dockerfile in the directory with this file. It guesses a name for the image. Builds the Dockerfile tagging that name using docker. For each command, expected_output pair in the unittest.yml file: run the image passing the command compares the expected_output(regex) against the output from the image exits if any images failed WIP
Approach taken from apptainer/singularity#429 (comment) 1. Creates docker container using local image. 2. Create singularity image 3. export docker image | import new singularity image
Other methods didn't fully setup singularity environment.
singularity was unable to reach the image registry Adding docker registry image to the circle config. Currently using circleci `docker` machine type. The `machine` machine type might resolve this issue but > Use of machine may require additional fees in a future pricing update. https://circleci.com/docs/2.0/executor-types/
this is to work around a cached venv from docker executor type that doesn't work under machine exexutor type
Also fixes picard unittest
singularity didn't like "trimmomatic:0.32+dfsg-1" on dockerhub its trimmomatic:0.32_dfsg-1
creates tests directory to hold image testing framework renames test.py to imagecheck
Adds more print commands so it is easier to see progress in the tests
This resulted in occasional connection reset by peer errors when running `docker push`.
Closing this for now due to the complexity and time it takes to run.
Both issues can be seen using just docker via the |
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.
Runs unit tests on images to make sure they will work with both docker and singularity.
test.py
look for files namedunitest.yml
. These files are assumed to be in a directory with a Dockerfile. Theunittest.yml
file will contain a list ofcommands
to run that contain acmd
andexpected_output
regex pattern.TODO