-
Notifications
You must be signed in to change notification settings - Fork 3
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
Test stability of pepper for contributors before 1st release #281
Comments
Dockerfile testNotes
in progress, will attach screenshots Build✔️Succeeded. Image builds w/o error PytestTested the following modules for successful run (all packages load):
Run.pyTested the following modules for a successful run (all packages load): DataTested the following modules for a successful run (all packages load):
PreprocessTested the following modules for a successful run (all packages load): |
Singularity Container TestNotes
PytestTested the following modules for successful run (all packages load):
Run.pyTested the following modules for successful run (all packages load):
DataTested the following modules for successful run (all packages load):
PreprocessTested the following modules for successful run (all packages load):
|
Conda TestNotes
PytestTested the following modules for successful run (all packages load):
Run.pyTested the following modules for a successful run (all packages load): DataTested the following modules for a successful run (all packages load): PreprocessTested the following modules for a successful run (all packages load): |
Revisit bind vs mount in closed discussion |
Resolved docker error via #306 |
Removing singularity stability test and moving to diff issue for closure |
Resolved singularity stability #307 |
Describe the feature to be tested
Before creating a discrete release its crucial to test the stability.
Which tests need to be made for the feature
This involves running all pytests over
Running regular pipeline over
As well as testing
And no new bugs are discovered.
This should be an automated process using Github actions eventually. Will record protocol and automate using Jenkins or Actions.
The text was updated successfully, but these errors were encountered: