Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a experimental PR to answer the following problematic:
When running test we often want to rerun the test without having to download back all the input data.
Sometimes we also just want to rerun the nf-test logic and not all the nextflow processing.
This PR introduce a new flag, that would have the same concept as the
--resumeof nextflow.The aim is to not reset the test folder, and let nextflow do it's resume job by adding this flag to the execution.
I would like to go even further by putting all the input into a separate folder to allow it to be shared across test.
It is often the case that different test case use the same input file but with different configuration. This would then allow to reduce the memory used.
What do you think ?