You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all of the Github Actions CI tests that we use to test that the pipeline functions (using a minimal dataset) are run as -profile test,docker. This just tests whether the pipeline will run with Docker, however, with the advent of DSL2 the processes we were using to create this Docker image are much more detached because the Conda, Singularity and Docker definitions are now all obtained from different sources. Developers tend to test with one of these methods so it would be great to have CI tests for all of them just to make sure they are working.
For example, I just noticed a Conda conflict issue because I explicitly tested -profile test,conda before releasing the rnaseq pipeline nf-core/rnaseq@c2a7fff.
The text was updated successfully, but these errors were encountered:
@drpatelh given that conda tests on CI are unreliable and testing for singularity might be an overkill for the runners, your thoughts on closing this issue?
Currently, all of the Github Actions CI tests that we use to test that the pipeline functions (using a minimal dataset) are run as
-profile test,docker
. This just tests whether the pipeline will run with Docker, however, with the advent of DSL2 the processes we were using to create this Docker image are much more detached because the Conda, Singularity and Docker definitions are now all obtained from different sources. Developers tend to test with one of these methods so it would be great to have CI tests for all of them just to make sure they are working.For example, I just noticed a Conda conflict issue because I explicitly tested
-profile test,conda
before releasing the rnaseq pipeline nf-core/rnaseq@c2a7fff.The text was updated successfully, but these errors were encountered: