Skip to content

Avoid "No outputs found matching patterns" when output is deliberately not created #153

Answered by wjchulme
wjchulme asked this question in Q&A
Discussion options

You must be logged in to vote

A couple of workarounds that will work for now:

a) Have the script create a dummy output file whenever that condition is not met, or always create the dummy file and have it overwritten whenever the condition is met.
b) Use catch-all pattern-matching so that as long as some files match the pattern, the error won't occur, for example output/*.txt

Replies: 1 comment

Comment options

wjchulme
Feb 12, 2021
Maintainer Author

You must be logged in to vote
0 replies
Answer selected by wjchulme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant